TEI Customization for the Srophé Application

Table of contents

1. Elements

1.1. <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Contained by
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<sch:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/> <sch:ns prefix="rna"  uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
Schematron
<sch:ns prefix="sch"  uri="http://purl.oclc.org/dsdl/schematron"/> <sch:ns prefix="sch1x"  uri="http://www.ascc.net/xml/schematron"/>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.resource"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="TEI" minOccurs="0"
     maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="TEI" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element TEI
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute version { text }?,
   ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}

1.2. <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
type(type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Note

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see 6.2.

Member of
Contained by
May contain
Note

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

1.3. <accMat>

<accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [11.7.3.3. Accompanying Material]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
Example
<accMat>A copy of a tax form from 1947 is included in the envelope with the letter. It is not catalogued separately.</accMat>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element accMat
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_macro.specialPara
}

1.4. <acquisition>

<acquisition> (acquisition) contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [11.8. History]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
msdescription: history
May contain
Example
<acquisition>Left to the <name type="place">Bodleian</name> by <name type="person">Richard Rawlinson</name> in 1755. </acquisition>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element acquisition
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.specialPara
}

1.5. <addName>

<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <forename>Frederick</forename>  <addName type="epithet">the Great</addName>  <roleName>Emperor of Prussia</roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addName
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.6. <addSpan>

<addSpan> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also <add>). [12.3.1.4. Additions and Deletions]
Moduletranscr
Attributes
Member of
Contained by
May containEmpty element
Note

Both the beginning and the end of the added material must be marked; the beginning by the <addSpan> element itself, the end by the spanTo attribute.

Example
<handNote xml:id="HEOL"  scribe="HelgiÓlafsson"/> <!-- ... --> <body>  <div> <!-- text here -->  </div>  <addSpan n="added_gatheringhand="#HEOL"   spanTo="#P025"/>  <div> <!-- text of first added poem here -->  </div>  <div> <!-- text of second added poem here -->  </div>  <div> <!-- text of third added poem here -->  </div>  <div> <!-- text of fourth added poem here -->  </div>  <anchor xml:id="P025"/>  <div> <!-- more text here -->  </div> </body>
Schematron
<sch:rule context="tei:addSpan"> <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:addSpan"> <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element addSpan
{
   tei_att.global.attributes,
   tei_att.transcriptional.attributes,
   tei_att.placement.attributes,
   tei_att.typed.attributes,
   tei_att.spanning.attributes,
   tei_att.dimensions.attributes,
   empty
}

1.7. <additional>

<additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [11.9. Additional Information]
Modulemsdescription
Attributes
Contained by
msdescription: msDesc msFrag msPart
May contain
core: listBibl p
msdescription: adminInfo surrogates
Example
<additional>  <adminInfo>   <recordHist>    <p> <!-- record history here -->    </p>   </recordHist>   <custodialHist>    <p> <!-- custodial history here -->    </p>   </custodialHist>  </adminInfo>  <surrogates>   <p> <!-- information about surrogates here -->   </p>  </surrogates>  <listBibl>   <bibl> <!-- ... -->   </bibl> <!-- full bibliography here -->  </listBibl> </additional>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="adminInfo"
    minOccurs="0"/>
   <elementRef key="surrogates"
    minOccurs="0"/>
   <elementRef key="listBibl" minOccurs="0"/>
  </sequence>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element additional
{
   tei_att.global.attributes,
   ( ( tei_adminInfo?, tei_surrogates?, tei_listBibl? ) | tei_model.pLike+ )
}

1.8. <additions>

<additions> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [11.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
Example
<additions>  <p>There are several marginalia in this manuscript. Some consist of    single characters and others are figurative. On 8v is to be found a drawing of    a mans head wearing a hat. At times sentences occurs: On 5v:  <q xml:lang="is">Her er skrif andres isslendin</q>,    on 19r: <q xml:lang="is">þeim go</q>,    on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad      batar þad mælgi ok mal</q>,    On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p> </additions>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element additions { tei_att.global.attributes, tei_macro.specialPara }

1.9. <adminInfo>

<adminInfo> (administrative information) contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. [11.9.1. Administrative Information]
Modulemsdescription
Attributes
Contained by
msdescription: additional
May contain
core: note
header: availability
msdescription: custodialHist recordHist
Example
<adminInfo>  <recordHist>   <source>Record created <date>1 Aug 2004</date>   </source>  </recordHist>  <availability>   <p>Until 2015 permission to photocopy some materials from this      collection has been limited at the request of the donor. Please ask repository staff for details      if you are interested in obtaining photocopies from Series 1:      Correspondence.</p>  </availability>  <custodialHist>   <p>Collection donated to the Manuscript Library by the Estate of      Edgar Holden in 1993. Donor number: 1993-034.</p>  </custodialHist> </adminInfo>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="recordHist"
   minOccurs="0"/>
  <elementRef key="availability"
   minOccurs="0"/>
  <elementRef key="custodialHist"
   minOccurs="0"/>
  <classRef key="model.noteLike"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element adminInfo
{
   tei_att.global.attributes,
   (
      tei_recordHist?,
      tei_availability?,
      tei_custodialHist?,
      tei_model.noteLike?
   )
}

1.10. <altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
msdescription: msFrag msIdentifier
May contain
Note

An identifying number of some kind must be supplied if known; if it is not known, this should be stated.

Example
<altIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </altIdentifier>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.placeNamePart"
   expand="sequenceOptional"/>
  <elementRef key="institution"
   minOccurs="0"/>
  <elementRef key="repository"
   minOccurs="0"/>
  <elementRef key="collection"
   minOccurs="0"/>
  <elementRef key="idno"/>
  <elementRef key="note" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element altIdentifier
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   (
      tei_placeName?,
      tei_bloc?,
      tei_country?,
      tei_region?,
      tei_settlement?,
      tei_district?,
      tei_institution?,
      tei_repository?,
      tei_collection?,
      tei_idno,
      tei_note?
   )
}

1.11. <am>

<am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [12.3.1.2. Abbreviation and Expansion]
Moduletranscr
Attributes
Member of
Contained by
May contain
Example
do you <abbr>Mr<am>.</am> </abbr> Jones?
Example
<choice>  <abbr>Aug<am>g</am>  </abbr>  <expan>Aug<ex>ustorum duo</ex>  </expan> </choice>
Example
<abbr>eu<am>   <g ref="#b-er"/>  </am>y</abbr> <abbr>  <am>   <g ref="#b-per"/>  </am>sone </abbr> ...
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.pPart.transcriptional"/>
 </alternate>
</content>
    
Schema Declaration
element am
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.editLike.attributes,
   ( text | tei_model.gLike | tei_model.pPart.transcriptional )*
}

1.12. <app>

<app> (apparatus entry) contains one entry in a critical apparatus, with an optional lemma and usually one or more readings or notes on the relevant passage. [13.1.1. The Apparatus Entry]
Moduletextcrit
Attributes
typeclassifies the variation contained in this element according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
fromidentifies the beginning of the lemma in the base text.
StatusOptional
Datatypeteidata.pointer
Note

This attribute should be used when either the double-end point method of apparatus markup, or the location-referenced method with a URL rather than canonical reference, are used.

toidentifies the endpoint of the lemma in the base text.
StatusOptional
Datatypeteidata.pointer
Note

This attribute is only used when the double-end point method of apparatus markup is used, when the encoded apparatus is not embedded in-line in the base-text.

loc(location) indicates the location of the variation, when the location-referenced method of apparatus markup is used.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Note

This attribute is used only when the location-referenced encoding method is used. It supplies a string containing a canonical reference for the passage to which the variation applies.

Member of
Contained by
May contain
core: note
Example
<app>  <lem wit="#El #Hg">Experience</lem>  <rdg wit="#Latype="substantive">Experiment</rdg>  <rdg wit="#Ra2type="substantive">Eryment</rdg> </app>
Example
<app type="substantive">  <rdgGrp type="subvariants">   <lem wit="#El #Hg">Experience</lem>   <rdg wit="#Ha4">Experiens</rdg>  </rdgGrp>  <rdgGrp type="subvariants">   <lem wit="#Cp #Ld1">Experiment</lem>   <rdg wit="#La">Ex<g ref="#per"/>iment</rdg>  </rdgGrp>  <rdgGrp type="subvariants">   <lem resp="#ed2013">Eriment</lem>   <rdg wit="#Ra2">Eryment</rdg>  </rdgGrp> </app>
Example
<app loc="1">  <rdg resp="#SEG">TIMΩΔA</rdg> </app>
Example
<app loc="1-6">  <note>Too badly worn to yield a text</note> </app>
Example
<choice xml:id="choice3">  <reg>σύμπαντα</reg>  <orig>ΣΙΝΠΑΤΑΝ</orig> </choice> <!-- ... --> <app from="#choice3">  <note>Mommsen's fanciful normalization, reproduced here, has not been accepted by all recent editions</note> </app>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="lem" minOccurs="0"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.rdgLike"/>
   <classRef key="model.noteLike"/>
   <elementRef key="witDetail"/>
   <elementRef key="wit"/>
   <elementRef key="rdgGrp"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element app
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute from { text }?,
   attribute to { text }?,
   attribute loc { list { + } }?,
   (
      tei_lem?,
      (
         tei_model.rdgLike
       | tei_model.noteLike
       | tei_witDetail
       | tei_wit
       | tei_rdgGrp
      )*
   )
}

1.13. <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
core: bibl
msdescription: msItem msItemStruct
May contain
namesdates: persName
character data
Note

The <author> element may contain either a <persName> element or text.

Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="persName"/>
  <textNode/>
 </alternate>
</content>
    
Schema Declaration
element author
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   ( tei_persName | text )*
}

1.14. <authority>

<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Contained by
May contain
Example
<authority>John Smith</authority>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element authority
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq.limited
}

1.15. <availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
status(status) supplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
Contained by
core: bibl
msdescription: adminInfo
May contain
core: p
header: licence
Note

A consistent format should be adopted

Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element availability
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( tei_model.availabilityPart | tei_model.pLike )+
}

1.16. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
transcr: facsimile
May contain
Note

Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical.

Example
<back>  <div type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets      and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she      had like to have been, too fond of Money <!-- .... -->   </p>  </div> <!-- ... -->  <div type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please;    <!-- ... -->   </p>  </div>  <div type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... -->    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div>  <div type="advert">   <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.      Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.        6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... -->   </list>  </div> </back>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divBottomPart"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element back
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      (
         tei_model.frontPart
       | tei_model.pLike.front
       | tei_model.pLike
       | tei_model.listLike
       | tei_model.global
      )*,
      (
         (
            tei_model.div1Like,
            ( tei_model.frontPart | tei_model.div1Like | tei_model.global )*
         )
       | (
            tei_model.divLike,
            ( tei_model.frontPart | tei_model.divLike | tei_model.global )*
         )
      )?,
      (
         tei_model.divBottomPart,
         ( tei_model.divBottomPart | tei_model.global )*
      )?
   )
}

1.17. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Note

Contains phrase-level elements, together with any combination of elements from the model.biblPart class

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="articlesubtype="book_chapter"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   tei_att.docStatus.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.highlighted
    | tei_model.pPart.data
    | tei_model.pPart.edit
    | tei_model.segLike
    | tei_model.ptrLike
    | tei_model.biblPart
    | tei_model.global
   )*
}

1.18. <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
Contained by
core: bibl
header: seriesStmt
May contain
core: title
header: idno
character data
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.

Example
<biblScope>pp 12–34</biblScope> <biblScope unit="pagefrom="12to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
Content model
<content>
 <elementRef key="title" minOccurs="0"
  maxOccurs="unbounded"/>
 <elementRef key="idno" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    
Schema Declaration
element biblScope
{
   tei_att.global.attributes,
   tei_att.citing.attributes,
   tei_title*,
   tei_idno*,
   text
}

1.19. <binding>

<binding> (binding) contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript or other object. [11.7.3.1. Binding Descriptions]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
contemporary(contemporary) specifies whether or not the binding is contemporary with the majority of its contents
StatusOptional
Datatypeteidata.xTruthValue
Note

The value true indicates that the binding is contemporaneous with its contents; the value false that it is not. The value unknown should be used when the date of either binding or manuscript is unknown

Contained by
msdescription: bindingDesc
May contain
core: p
msdescription: condition decoNote
Example
<binding contemporary="true">  <p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp    closing to the back cover.</p> </binding>
Example
<bindingDesc>  <binding contemporary="false">   <p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front      pastedown.</p>  </binding>  <binding contemporary="false">   <p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p>  </binding> </bindingDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <elementRef key="condition"/>
  <elementRef key="decoNote"/>
 </alternate>
</content>
    
Schema Declaration
element binding
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   attribute contemporary { text }?,
   ( tei_model.pLike | tei_condition | tei_decoNote )+
}

1.20. <bindingDesc>

<bindingDesc> (binding description) describes the present and former bindings of a manuscript or other object, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript. [11.7.3.1. Binding Descriptions]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: binding condition decoNote
Example
<bindingDesc>  <p>Sewing not visible; tightly rebound over    19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with    gilt tooling à la fanfare, Paris c. 1580-90, the centre of each    cover inlaid with a 17th-cent. oval medallion of red morocco tooled in    gilt (perhaps replacing the identifying mark of a previous owner); the    spine similarly tooled, without raised bands or title-piece; coloured    endbands; the edges of the leaves and boards gilt.Boxed.</p> </bindingDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.pLike"/>
   <elementRef key="decoNote"/>
   <elementRef key="condition"/>
  </alternate>
  <elementRef key="binding" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element bindingDesc
{
   tei_att.global.attributes,
   ( ( tei_model.pLike | tei_decoNote | tei_condition )+ | tei_binding+ )
}

1.21. <birth>

<birth> (birth) contains information about a person's birth, such as its date and place. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person personGrp
May contain
Example
<birth>Before 1920, Midlands region.</birth>
Example
<birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>, early in the morning of <date>10 Dec 1960</date> </birth>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element birth
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.dimensions.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.22. <bloc>

<bloc> (bloc) contains the name of a geo-political unit consisting of two or more nation states or countries. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<bloc type="union">the European Union</bloc> <bloc type="continent">Africa</bloc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element bloc
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.23. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divTop"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divGenLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <alternate minOccurs="0" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element body
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      tei_model.global*,
      ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )?,
      ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?,
      (
         ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+
       | ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+
       | (
            ( ( schemaSpec | tei_model.common ), tei_model.global* )+,
            (
               (
                  tei_model.divLike,
                  ( tei_model.global | tei_model.divGenLike )*
               )+
             | (
                  tei_model.div1Like,
                  ( tei_model.global | tei_model.divGenLike )*
               )+
            )?
         )
      ),
      ( tei_model.divBottom, tei_model.global* )*
   )
}

1.24. <catDesc>

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
header: category
May contain
Note

The <catDesc> contains a brief prose description of the category’s purpose.

Example
<classDecl>  <taxonomy>   <category xml:id="syriaca-headword">    <catDesc>The name used by Syriaca.org for document titles, citation, and        disambiguation. These names have been created according to the Syriac.org        guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc>   </category>  </taxonomy> </classDecl>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.catDescPart"/>
 </alternate>
</content>
    
Schema Declaration
element catDesc
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   ( text | tei_model.limitedPhrase | tei_model.catDescPart )*
}

1.25. <catchwords>

<catchwords> (catchwords) describes the system used to ensure correct ordering of the quires or similar making up a codex, incunable, or other object typically by means of annotations at the foot of the page. [11.3.7. Catchwords, Signatures, Secundo Folio]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<catchwords>Vertical catchwords in the hand of the scribe placed along the inner bounding line, reading from top to bottom.</catchwords>
Schematron
<sch:rule context="tei:catchwords"> <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element catchwords { tei_att.global.attributes, tei_macro.phraseSeq }

1.26. <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
May contain
core: desc
Note

The <category> has an xml:id attribute whose value is the tag. Within the <category> element is a <catDesc> element which contains a brief prose description of the category’s purpose.

Example
<classDecl>  <taxonomy>   <category xml:id="syriaca-headword">    <catDesc>The name used by Syriaca.org for document titles, citation, and        disambiguation. These names have been created according to the Syriac.org        guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc>   </category>  </taxonomy> </classDecl>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="catDesc" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   (
      ( tei_catDesc+ | ( tei_model.descLike | equiv | gloss )* ),
      tei_category*
   )
}

1.27. <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
Derived fromatt.ascribed
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusRequired
Datatypeteidata.temporal.w3c
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
target(target) points to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
msdescription: recordHist
May contain
Note

The <change> element takes attributes when and who which indicate the date of the change and the person who made the change. The value of when is a date in "yyyy-mm-dd" format, whereas who will have the value of an xml:id attribute from "http://syriaca.org/documentation/editors.xml" - the list of editors. An optional n attribute whose value is a version number can indicate that this change advanced the version number (given in the <editionStmt> within the <fileDesc> element). The contents of the <change> element describe the revision that was made.

Example
<revisionDesc>  <change when="2013-04-15"   who="http://syriaca.org/documentation/editors.xml#ngibsonn="1.1"> ADDED: Pleiades coordinates</change>  <change when="2013-04-01"   who="http://syriaca.org/documentation/editors.xml#dmichelson"> FIXED: Ufra to    Urfa</change>  <change when="2013-03-16"   who="http://syriaca.org/documentation/editors.xml#tcarlsonn="1.0"> ADDED:    teiHeader/revisionDesc</change>  <change when="2013-03-15"   who="http://syriaca.org/documentation/editors.xml#tcarlson"> ADDED:    teiHeader</change>  <change when="2013-03-01"   who="http://syriaca.org/documentation/editors.xml#tcarlsonn="0.1"> CREATED:    place</change> </revisionDesc>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   tei_att.datable.attribute.srophecomputed-start,
   tei_att.datable.attribute.srophecomputed-end,
   tei_att.datable.attribute.period,
   tei_att.datable.w3c.attribute.notBefore,
   tei_att.datable.w3c.attribute.notAfter,
   tei_att.datable.w3c.attribute.from,
   tei_att.datable.w3c.attribute.to,
   tei_att.datable.iso.attribute.when-iso,
   tei_att.datable.iso.attribute.notBefore-iso,
   tei_att.datable.iso.attribute.notAfter-iso,
   tei_att.datable.iso.attribute.from-iso,
   tei_att.datable.iso.attribute.to-iso,
   tei_att.datable.custom.attribute.when-custom,
   tei_att.datable.custom.attribute.notBefore-custom,
   tei_att.datable.custom.attribute.notAfter-custom,
   tei_att.datable.custom.attribute.from-custom,
   tei_att.datable.custom.attribute.to-custom,
   tei_att.datable.custom.attribute.datingPoint,
   tei_att.datable.custom.attribute.datingMethod,
   tei_att.docStatus.attributes,
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.rendition.attribute.style,
   tei_att.global.rendition.attribute.rendition,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.facs.attribute.facs,
   tei_att.global.change.attribute.change,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.global.source.attribute.source,
   tei_att.typed.attributes,
   attribute who { list { + } },
   attribute when { text },
   attribute n { text }?,
   attribute calendar { list { + } }?,
   attribute target { list { + } }?,
   tei_macro.specialPara
}

1.28. <choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Modulecore
Attributes
Member of
Contained by
May contain
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 13.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

ExampleAn American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>   <sic>1724</sic>   <corr>1728</corr>  </choice> of our subjects, with free access to our royal person, and other marks of our <choice>   <orig>favour</orig>   <reg>favor</reg>  </choice>.</p>
Content model
<content>
 <alternate minOccurs="2"
  maxOccurs="unbounded">
  <classRef key="model.choicePart"/>
  <elementRef key="choice"/>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   ( tei_model.choicePart | tei_choice )+
}

1.29. <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Derived fromatt.citing
StatusRequired
Datatypeteidata.enumerated
Legal values are:
book
the element identifies a book, typically a numbered portion of an ancient work
chapter
the element identifies a chapter by number, title, or both
col
the element identifies a column or column range
entry
the element identifies an entry in a collection such as an reference work
fig
the element identifies a figure, i.e. a graphic, table, etc.
fol
the element identifies a folio number or folio range
line
the element contains a line number or line range
map
the element identifies a map
note
the element identifies a footnote or endnote
part
the element contains a part of a book or collection, i.e. chapter and verse of a biblical text
p
the element contains a page number or page range
section
the element identifies a section of a text
URL
the element identifies a URL where information is located
vol
the element identifies a volume of a multi-volume work
Member of
Contained by
core: bibl
May contain
Note

The <citedRange> is used to indicate the portion of a text is being cited in a bibliographic reference. It requires a unit attribute with one of the following values: col, entry, fol, line, map, part, p, section, and vol.

Example
<citedRange>pp 12–13</citedRange> <citedRange unit="pagefrom="12to="13"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange>
Example
<bibl>  <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.    4-5</citedRange> </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.citing.attribute.from,
   tei_att.citing.attribute.to,
   attribute unit
   {
      "book"
    | "chapter"
    | "col"
    | "entry"
    | "fig"
    | "fol"
    | "line"
    | "map"
    | "note"
    | "part"
    | "p"
    | "section"
    | "URL"
    | "vol"
   },
   tei_macro.phraseSeq
}

1.30. <classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Moduleheader
Attributes
Contained by
header: encodingDesc
May contain
header: taxonomy
Note

The <classDecl> contains one or more taxonomies defining any classificatory codes used elsewhere in the text. There are various tags which Syriaca.org uses to mark elements for a variety of purposes. Syriaca.org’s preferred name forms are tagged with "syriaca-headword", for example.

Example
<classDecl>  <taxonomy>   <category xml:id="syriaca-headword">    <catDesc>The name used by Syriaca.org for document titles, citation, and        disambiguation. These names have been created according to the Syriac.org        guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc>   </category>  </taxonomy> </classDecl>
Content model
<content>
 <elementRef key="taxonomy" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element classDecl { tei_att.global.attributes, tei_taxonomy+ }

1.31. <collation>

<collation> (collation) contains a description of how the leaves, bifolia, or similar objects are physically arranged. [11.7.1. Object Description]
Modulemsdescription
Attributes
Contained by
msdescription: supportDesc
May contain
Example
<collation>The written leaves preceded by an original flyleaf, conjoint with the pastedown.</collation>
Example
<collation>  <p>   <formula>1-5.8 6.6 (catchword, f. 46, does not match following text)      7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula>   <catchwords>Catchwords are written horizontally in center      or towards the right lower margin in various manners:      in red ink for quires 1-6 (which are also signed in red      ink with letters of the alphabet and arabic numerals);      quires 7-9 in ink of text within yellow decorated frames;      quire 10 in red decorated frame; quire 12 in ink of text;      quire 13 with red decorative slashes; quire 14 added in      cursive hand.</catchwords>  </p> </collation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element collation { tei_att.global.attributes, tei_macro.specialPara }

1.32. <collection>

<collection> (collection) contains the name of a collection of manuscripts or other objects, not necessarily located within a single repository. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
Contained by
May contain
Example
<msIdentifier>  <country>USA</country>  <region>California</region>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <collection>Ellesmere</collection>  <idno>El 26 C 9</idno>  <msName>The Ellesmere Chaucer</msName> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element collection
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq.limited
}

1.33. <colophon>

<colophon> (colophon) contains the colophon of an item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript or other object. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Example
<colophon>Ricardus Franciscus Scripsit Anno Domini 1447.</colophon>
Example
<colophon>Explicit expliceat/scriptor ludere eat.</colophon>
Example
<colophon>Explicit venenum viciorum domini illius, qui comparavit Anno domini Millessimo Trecentesimo nonagesimo primo, Sabbato in festo sancte Marthe virginis gloriose. Laus tibi criste quia finitur libellus iste.</colophon>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element colophon
{
   tei_att.global.attributes,
   tei_att.msExcerpt.attributes,
   tei_macro.phraseSeq
}

1.34. <condition>

<condition> (condition) contains a description of the physical condition of the manuscript or object. [11.7.1.5. Condition]
Modulemsdescription
Attributes
Contained by
May contain
Example
<condition>  <p>There are lacunae in three places in this    manuscript. After 14v two    leaves has been cut out and narrow strips leaves remains in the spine. After    68v one gathering is missing and after 101v at least one gathering of 8 leaves    has been lost. </p>  <p>Several leaves are damaged with tears or holes or have a    irregular shape. Some of the damages do not allow the lines to be of full    length and they are apparently older than the script. There are tears on fol.    2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,    37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,    74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98    the corner has been torn off. Several leaves are in a bad condition due to    moist and wear, and have become dark, bleached or    wrinkled. </p>  <p>The script has been    touched up in the 17th century with black ink. The touching up on the following    fols. was done by  <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,    6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An    AM-note says according to the lawman  <name>Sigurður Björnsson</name> that the rest of the    touching up was done by himself and another lawman  <name>Sigurður Jónsson</name>.  <name>Sigurður Björnsson</name> did the touching up    on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.  <name>Sigurður Jónsson</name> did the rest of the    touching up in the section 36r-59r containing  <title>Bretasögur</title>  </p> </condition>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element condition { tei_att.global.attributes, tei_macro.specialPara }

1.35. <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element corr
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.36. <country>

<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

The recommended source for codes to represent coded country names is ISO 3166.

Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element country
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.37. <custEvent>

<custEvent> (custodial event) describes a single event during the custodial history of a manuscript or other object. [11.9.1.2. Availability and Custodial History]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
msdescription: custodialHist
May contain
Example
<custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date> </custEvent>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element custEvent
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   tei_macro.specialPara
}

1.38. <custodialHist>

<custodialHist> (custodial history) contains a description of a manuscript or other object's custodial history, either as running prose or as a series of dated custodial events. [11.9.1.2. Availability and Custodial History]
Modulemsdescription
Attributes
Contained by
msdescription: adminInfo
May contain
core: p
msdescription: custEvent
Example
<custodialHist>  <custEvent type="conservation"   notBefore="1961-03notAfter="1963-02">Conserved between March 1961 and February 1963 at    Birgitte Dalls Konserveringsværksted.</custEvent>  <custEvent type="photography"   notBefore="1988-05-01notAfter="1988-05-30">Photographed in    May 1988 by AMI/FA.</custEvent>  <custEvent type="transfer-dispatch"   notBefore="1989-11-13notAfter="1989-11-13">Dispatched to Iceland    13 November 1989.</custEvent> </custodialHist>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="custEvent" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element custodialHist
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | tei_custEvent+ )
}

1.39. <damage>

<damage> (damage) contains an area of damage to the text witness. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Attributes
Member of
Contained by
May contain
Note

Since damage to text witnesses frequently makes them harder to read, the <damage> element will often contain an <unclear> element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related <damage> elements; alternatively the <join> element may be used to indicate which <damage> and <unclear> elements are part of the same physical phenomenon.

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

Example
<l>The Moving Finger wri<damage agent="watergroup="1">es; and</damage> having writ,</l> <l>Moves <damage agent="watergroup="1">   <supplied>on: nor all your</supplied>  </damage> Piety nor Wit</l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element damage
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.damaged.attributes,
   tei_macro.paraContent
}

1.40. <damageSpan>

<damageSpan> (damaged span of text) marks the beginning of a longer sequence of text which is damaged in some way but still legible. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Attributes
Member of
Contained by
May containEmpty element
Note

Both the beginning and ending of the damaged sequence must be marked: the beginning by the <damageSpan> element, the ending by the target of the spanTo attribute: if no other element available, the <anchor> element may be used for this purpose.

The damaged text must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <damageSpan> element should not be used. Rather, the <gap> or <unclear> element should be employed, with the value of the reason attribute giving the cause. See further sections 12.3.3.1. Damage, Illegibility, and Supplied Text and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.

Example
<p>Paragraph partially damaged. This is the undamaged portion <damageSpan spanTo="#a34"/>and this the damaged portion of the paragraph.</p> <p>This paragraph is entirely damaged.</p> <p>Paragraph partially damaged; in the middle of this paragraph the damage ends and the anchor point marks the start of the <anchor xml:id="a34"/> undamaged part of the text. ...</p>
Schematron
<sch:rule context="tei:damageSpan"> <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:damageSpan"> <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element damageSpan
{
   tei_att.global.attributes,
   tei_att.damaged.attributes,
   tei_att.typed.attributes,
   tei_att.spanning.attributes,
   empty
}

1.41. <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.calendarSystem.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

1.42. <death>

<death> (death) contains information about a person's death, such as its date and place. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Note

This attribute is not intended to express the cause of death.

calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person personGrp
May contain
Example
<death when="1902-10-01"/>
Example
<death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element death
{
   tei_att.datable.attributes,
   tei_att.dimensions.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.43. <decoDesc>

<decoDesc> (decoration description) contains a description of the decoration of a manuscript or other object, either as in paragraphs, or as one or more <decoNote> elements. [11.7.3. Bindings, Seals, and Additional Material]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: decoNote summary
Example
<decoDesc>  <p>The start of each book of the Bible with a 10-line historiated    illuminated initial; prefaces decorated with 6-line blue initials with red    penwork flourishing; chapters marked by 3-line plain red initials; verses    with 1-line initials, alternately blue or red.</p> </decoDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="decoNote" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element decoDesc
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_summary?, tei_decoNote+ ) )
}

1.44. <decoNote>

<decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript or other object, or a fairly homogenous class of such components. [11.7.3. Bindings, Seals, and Additional Material]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<decoDesc>  <decoNote type="initial">   <p>The start of each book of the Bible with      a 10-line historiated illuminated initial;      prefaces decorated with 6-line blue initials      with red penwork flourishing; chapters marked by      3-line plain red initials; verses with 1-line initials,      alternately blue or red.</p>  </decoNote> </decoDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element decoNote
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_macro.specialPara
}

1.45. <delSpan>

<delSpan> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [12.3.1.4. Additions and Deletions]
Moduletranscr
Attributes
Member of
Contained by
May containEmpty element
Note

Both the beginning and ending of the deleted sequence must be marked: the beginning by the <delSpan> element, the ending by the target of the spanTo attribute.

The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <delSpan> tag should not be used. Rather, the <gap> tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the <unclear> element should be used to signal the areas of text which cannot be read with confidence. See further sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and, for the close association of the <delSpan> tag with the <gap>, <damage>, <unclear> and <supplied> elements, 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.

The <delSpan> tag should not be used for deletions made by editors or encoders. In these cases, either the <corr> tag or the <gap> tag should be used.

Example
<p>Paragraph partially deleted. This is the undeleted portion <delSpan spanTo="#a23"/>and this the deleted portion of the paragraph.</p> <p>Paragraph deleted together with adjacent material.</p> <p>Second fully deleted paragraph.</p> <p>Paragraph partially deleted; in the middle of this paragraph the deletion ends and the anchor point marks the resumption <anchor xml:id="a23"/> of the text. ...</p>
Schematron
<sch:rule context="tei:delSpan"> <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:delSpan"> <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element delSpan
{
   tei_att.global.attributes,
   tei_att.transcriptional.attributes,
   tei_att.typed.attributes,
   tei_att.spanning.attributes,
   tei_att.dimensions.attributes,
   empty
}

1.46. <depth>

<depth> (depth) contains a measurement from the front to the back of an object, perpendicular to the measurement given by the <width> element. [11.3.4. Dimensions]
Modulemsdescription
Attributes
Member of
Contained by
May containCharacter data only
Example
<depth unit="inquantity="4"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element depth
{
   tei_att.global.attributes,
   tei_att.dimensions.attributes,
   tei_macro.xtext
}

1.47. <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
<dataSpec module="tei"  ident="teidata.point"  validUntil="2050-02-25">  <desc type="deprecationInfo"   versionDate="2018-09-14"   xml:lang="en">Several standards bodies, including NIST in the USA,    strongly recommend against ending the representation of a number    with a decimal point. So instead of <q>3.</q> use either <q>3</q>    or <q>3.0</q>.</desc> <!-- ... --> </dataSpec>
Member of
Contained by
May contain
Note

When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.

ExampleExample of a <desc> element inside a documentation element.
<dataSpec module="tei"  ident="teidata.point">  <desc versionDate="2010-10-17"   xml:lang="en">defines the data type used to express a point in cartesian space.</desc>  <content>   <dataRef name="token"    restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>  </content> <!-- ... --> </dataSpec>
ExampleExample of a <desc> element in a non-documentation element.
<place xml:id="KERG2">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
SchematronA <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   tei_att.global.attributes,
   tei_att.translatable.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { text }?,
   tei_macro.limitedContent
}

1.48. <dim>

<dim> contains any single measurement forming part of a dimensional specification of some sort. [11.3.4. Dimensions]
Modulemsdescription
Attributes
Member of
Contained by
May containCharacter data only
Note

The specific elements <width>, <height>, and <depth> should be used in preference to this generic element wherever appropriate.

Example
<dim type="circumferenceextent="4.67 in"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element dim
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_macro.xtext
}

1.49. <dimensions>

<dimensions> (dimensions) contains a dimensional specification. [11.3.4. Dimensions]
Modulemsdescription
Attributes
typeindicates which aspect of the object is being measured.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Member of
Contained by
May contain
msdescription: depth dim height width
Note

Contains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.

Example
<dimensions type="leaves">  <height scope="range">157-160</height>  <width>105</width> </dimensions> <dimensions type="ruled">  <height scope="most">90</height>  <width scope="most">48</width> </dimensions> <dimensions unit="in">  <height>12</height>  <width>10</width> </dimensions>
ExampleThis element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:
<dimensions type="panels">  <height scope="all">7004</height>  <width scope="all">1803</width>  <dim type="reliefunit="mm">345</dim> </dimensions>
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
ExampleWhen simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:
<dimensions type="leaves">  <height scope="range">157-160</height>  <width quantity="105"/> </dimensions> <dimensions type="ruled">  <height unit="cmscope="most"   quantity="90"/>  <width unit="cmscope="mostquantity="48"/> </dimensions> <dimensions unit="in">  <height quantity="12"/>  <width quantity="10"/> </dimensions>
Schematron
<sch:rule context="tei:dimensions"> <sch:report test="count(tei:width) gt 1"> The element <sch:name/> may appear once only </sch:report> <sch:report test="count(tei:height) gt 1"> The element <sch:name/> may appear once only </sch:report> <sch:report test="count(tei:depth) gt 1"> The element <sch:name/> may appear once only </sch:report> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="dim"/>
  <classRef key="model.dimLike"/>
 </alternate>
</content>
    
Schema Declaration
element dimensions
{
   tei_att.global.attributes,
   tei_att.dimensions.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   ( tei_dim | tei_model.dimLike )*
}

1.50. <district>

<district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <district type="ward">Jericho</district>  <settlement>Oxford</settlement> </placeName>
Example
<placeName>  <district type="area">South Side</district>  <settlement>Chicago</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element district
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.51. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
Member of
Contained by
textcrit: lem rdg
textstructure: back body div front
May contain
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number [...]</p>    <div n="1.1type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority [...] </p>    </div>    <div n="1.2type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when [...] </p>    </div>   </div>  </div> </body>
Schematron
<sch:rule context="tei:div"> <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:div"> <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   tei_att.written.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            ( ( tei_model.divLike | tei_model.divGenLike ), tei_model.global* )+
          | (
               ( ( schemaSpec | tei_model.common ), tei_model.global* )+,
               (
                  ( tei_model.divLike | tei_model.divGenLike ),
                  tei_model.global*
               )*
            )
         ),
         ( tei_model.divBottom, tei_model.global* )*
      )?
   )
}

1.52. <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader
Attributes
Member of
Contained by
core: bibl
header: editionStmt
May contain
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element edition { tei_att.global.attributes, tei_macro.phraseSeq }

1.53. <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
header: edition
Note

The <editionStmt> allows the specification of an edition or version number. When a TEI file is first published online, that edition should be "1.0". Subsequent revisions may bump the revision number, either by a whole new version (i.e. to "2.0") or by a minor version (i.e. to "1.1").

Example
<editionStmt>  <edition n="1.0"/> </editionStmt>
Content model
<content>
 <elementRef key="edition" minOccurs="1"
  maxOccurs="1"/>
</content>
    
Schema Declaration
element editionStmt { tei_att.global.attributes, tei_edition }

1.54. <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
roleSpecifies the connection of the editor to the work, selected from http://syriaca.org/documentation/author-editor-roles.xml . The attribute value should contain the above URL followed by a hash (#) and the xml:id of the role. For example, http://syriaca.org/documentation/author-editor-roles.xml#translator . This is recommended, but not required if the type of connection is unknown.
Derived fromatt.naming
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
associate
An associate editor
code-author
The person responsible for the creation of the xml encoding
content-author
The person responsible for the content encoded in this document by another person
contributor
A person who contributed some data but is not the main person responsible for the document
creator
The main author responsible for the document
editor
An editor as defined by the Chicago Manual of Style
general
A general editor of a module
past-associate
A former associate editor
past-general
A former general editor of a module
past-technical
A former editor responsible for the data model
technical
An editor responsible for the data model
translator
The translator of a text
ref(reference) Should contain the URI of a Syriaca.org editor from this list.
Derived fromatt.canonical
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
core: bibl
msdescription: msItem
May contain
core: date
namesdates: persName
character data
Note

The <editor> element is used in three places in the Srophé App. In the <teiHeader> the editors of the document appear inside the <titleStmt> element while inside the <seriesStmt> the editors responsible for a series that the document might be a part of are listed. In the text of files, the <editor> element is used inside of <bibl> elements to indicated editors of works sited.

Example
<editor ref="http://syriaca.org/person/239"  role="http://syriaca.org/documentation/author-editor-roles.xml#translator">  <persName xml:lang="en">Gregorius Bar Hebraeus</persName><persName xml:lang="syr">ܓܪܝܓܘܪܝܘܣ ܒܪ ܥܒܪܝܐ</persName> </editor>
Example
<editor role="creator"  ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas A. Carlson</editor>
Example
<bibl xml:id="bib18-9">  <title xml:lang="en">The Sixth Book of the Select Letters of Severus, Patriarch of    Antioch in the Syriac Version of Athanasius of Nisibis</title>  <title type="sub">Translation, I.1 - II.3</title>  <author>   <persName ref="http://syriaca.org/person/51">Severus of Antioch</persName>  </author>  <editor>   <persName ref="http://syriaca.org/person/403">E. W. Brooks</persName>  </editor>  <ptr target="http://syriaca.org/bibl/668"/>  <citedRange unit="p">151</citedRange> </bibl>
Example
<titleStmt>  <title level="axml:lang="en">Telneshe — <foreign xml:lang="syr">ܬܠܢܫܐ</foreign>  </title> ... <editor role="code-author"   ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas A.    Carlson</editor>  <editor role="content-author"   ref="http://syriaca.org/documentation/editors.xml#dboero">Dina Boero</editor>  <respStmt>   <resp>Initial XML by</resp>   <name ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas A.      Carlson</name>  </respStmt>  <respStmt>   <resp>Data submission by</resp>   <name ref="http://syriaca.org/documentation/editors.xml#dboero">Dina Boero</name>  </respStmt>  <respStmt>   <resp>Data submission review by</resp>   <name ref="http://syriaca.org/documentation/editors.xml#pforness">Philip      Forness</name>  </respStmt> </titleStmt>
Example
<seriesStmt>  <title level="sxml:lang="en">The Syriac Gazetteer</title>  <editor role="general"   ref="http://syriaca.org/documentation/editors.xml#dmichelson">   <persName>David A. Michelson</persName>, <date from="2014">2014-present</date>.</editor>  <editor role="general"   ref="http://syriaca.org/documentation/editors.xml#wpotter">   <persName>William L. Potter</persName>, <date from="2020">2020-present</date>.</editor>  <editor role="technical"   ref="http://syriaca.org/documentation/editors.xml#dschwartz">   <persName>Daniel L. Schwartz</persName>, <date from="2019">2019-present</date>.</editor>  <editor role="past-general"   ref="http://syriaca.org/documentation/editors.xml#tcarlson">   <persName>Thomas A. Carlson</persName>, <date from="2014to="2018">2014-2018</date>  </editor>  <idno type="URI">http://syriaca.org/geo</idno> </seriesStmt>
Schematron
<sch:rule context="//tei:teiHeader//tei:editor"> <sch:assert test="./@role">A @role attribute is required on the <editor> element inside <teiHeader>.</sch:assert> </sch:rule> <sch:rule context="//tei:teiHeader//tei:titleStmt//tei:editor/@role"> <sch:assert test=". = 'creator' or . = 'code-author' or . = 'content-author' or . = 'contributor'"> The acceptable attribute values for @role on the <editor> element inside the <titleStmt> are: creator, code-author, content-author, or contributor. </sch:assert> </sch:rule> <sch:rule context="//tei:teiHeader//tei:seriesStmt//tei:editor/@role"> <sch:assert test=". = 'associate' or . = 'general' or . = 'technical' or . = 'past-associate' or . = 'past-general' or . = 'past-technical'"> The acceptable attribute values for @role on the <editor> element inside the <seriesStmt> are: associate, general, technical, past-associate, past-general, or past-technical. </sch:assert> </sch:rule> <sch:rule context="//tei:body//tei:editor/@role"> <sch:assert test=". = 'editor' or . = 'general' or . = 'translator'"> The acceptable attribute values for @role on the <editor> element inside the <body> are: editor, general, or translator. </sch:assert> </sch:rule>
Schematron
<sch:rule context="//tei:teiHeader//tei:seriesStmt//tei:editor[contains(@role, 'past')]"> <sch:assert test="tei:date">An <editor> element with a "past" @role attribute must contain a <date> element.</sch:assert> </sch:rule>
Schematron
<sch:rule context="//tei:teiHeader//tei:editor"> <sch:assert test="./@ref">A @ref attribute is required on the <editor> element inside <teiHeader>.</sch:assert> </sch:rule> <sch:rule context="//tei:teiHeader//tei:editor/@ref"> <sch:let name="edsDoc"  value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/editors.xml')"/> <sch:let name="eds"  value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id"/> <sch:let name="refValues"  value="for $i in $eds return concat('http://syriaca.org/documentation/editors.xml#', $i)"/> <sch:assert test="every $i in . satisfies $i = $refValues"> Acceptable values for the @ref attribute on an <editor> element inside the <teiHeader> include: <sch:value-of select="string-join($refValues, ' | ')"/>. </sch:assert> </sch:rule> <sch:rule context="//tei:body//tei:editor"> <sch:report test="./@ref">A @ref attribute is not allowed on the <editor> element inside <body>.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="persName"/>
  <elementRef key="date"/>
  <textNode/>
 </alternate>
</content>
    
Schema Declaration
element editor
{
   tei_att.global.attributes,
   tei_att.naming.attribute.nymRef,
   tei_att.canonical.attribute.key,
   tei_att.datable.attributes,
   attribute role
   {
      list
      {
         (
            "associate"
          | "code-author"
          | "content-author"
          | "contributor"
          | "creator"
          | "editor"
          | "general"
          | "past-associate"
          | "past-general"
          | "past-technical"
          | "technical"
          | "translator"
         )+
      }
   }?,
   attribute ref { list { + } }?,
   attribute calendar { list { + } }?,
   ( tei_persName | tei_date | text )*
}

1.55. <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Contained by
header: encodingDesc
May contain
core: p
Note

The first element within an <encodingDesc> is the <editorialDecl>, which indicates editorial decisions regarding how the source documents were handled. An <editorialDecl> cannot directly contain prose, so a prose description of each editorial decision should be wrapped in a <p> element. References to particular bibliographic entries can have their Syriaca.org URIs wrapped in an <idno> for specificity. The first <p> element should contain a pointer to the Syriaca.org documentation.

Example
<encodingDesc>  <editorialDecl>   <p>This record created following the Syriaca.org guidelines. Documentation      available at: <ref target="http://syriaca.org/documentation"> http://syriaca.org/documentation</ref>.</p>   <p>The capitalization of names from GEDSH (<idno type="URI">http://syriaca.org/bibl/1</idno>) was normalized (i.e. names in ALL-CAPS were      replaced by Proper-noun capitalization).</p>   <p>The unchanging parts of alternate names from Barsoum (<idno type="URI">http://syriaca.org/bibl/2</idno>, <idno type="URI">http://syriaca.org/bibl/3</idno>, or <idno type="URI">http://syriaca.org/bibl/4</idno>) have been supplied to each alternate.</p>   <p>Names from the English translation of Barsoum (<idno type="URI">http://syriaca.org/bibl/4</idno>) were put in sentence word order rather than      fronting a dictionary headword. Any commas in the Barsoum name in English were      removed.</p>   <p>The <gi>state</gi> element of @type="existence" indicates the period for which      this place was in use as a place of its indicated type (e.g. an inhabited      settlement, a functioning monastery or church, an administrative province).      Natural features always in existence have no <gi>state</gi> element of      @type="existence".</p> ... </editorialDecl> ... </encodingDesc>
Content model
<content>
 <elementRef key="p" minOccurs="1"
  maxOccurs="unbounded"/>
 <elementRef key="interpretation"
  minOccurs="0" maxOccurs="1"/>
</content>
    
Schema Declaration
element editorialDecl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_p+,
   tei_interpretation?
}

1.56. <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
Note

The <encodingDesc> element of the <teiHeader> is used for indicating aspects of the process of encoding the text. Even data are "born digital," they nevertheless have certain editorial decisions regarding how they have used data derived from print resources, and certain tags available for use in our srophe:tags attribute. Those sorts of details are encoded here.

Example
<encodingDesc>  <editorialDecl>   <p>This record has been created following the Syriaca.org editorial guidelines.      Documentation is available at: <ref target="http://syriaca.org/documentation">http://syriaca.org/documentation</ref>. <title>The Syriac Gazetteer</title>      was encoded using both the general editorial guidelines for all publications of      Syriaca.org and an encoding schema specific to <title>The Syriac        Gazetteer</title>.</p>   <p>Approximate dates described in terms of centuries or partial centuries have      been interpreted into quantitative values as documented in the Syriaca.org      guidelines for normalization of dates. See <ref target="http://syriaca.org/documentation/dates.html">Syriaca.org Guidelines        for Approximate Dates</ref>.</p>   <p>The <gi>state</gi> element of @type="existence" indicates the period for which      this place was in use as a place of its indicated type (e.g. an inhabited      settlement, a functioning monastery or church, an administrative province).      While it is possible to indicate a source for this date, this date is usually      based on the estimate of the editors and provided as an aid to searching. As a      practice, attested dates for a place based on historical sources have instead      been encoded more precisely using <gi>event</gi> of @type="attestation". Natural      features which have always existed have no date on the <gi>state</gi> element of      @type="existence" since they are are presumed to have always existed throughout      recorded history.</p>   <p>In some cases, maps from print publications have been used as the basis for      coordinate data in <title>The Syriac Gazetteer</title>. In two instances, the      editors of such print maps provided the digital coordinate data used to prepare      the print maps. Specifically, coordinates which are attributed to <title>The        Gorgias Encyclopedic Dictionary of the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) or to   <title>The Syriac World</title> (<ref target="http://syriaca.org/bibl/PUTG99V4">http://syriaca.org/bibl/PUTG99V4</ref>) were extracted from the KML files      used to create the print maps for those volumes. Because only the print maps      were published, the citation for these coordinates refers to the print source.      The editors of the <title>The Syriac Gazetteer</title> are grateful to the      editors of <title>The Gorgias Encyclopedic Dictionary of the Syriac        Heritage</title> and <title>The Syriac World</title> for providing these      coordinate files.</p>   <p>The editors have silently normalized data from other sources in some cases. The      primary instances are listed below.</p>   <p>The capitalization of names from <title>The Gorgias Encyclopedic Dictionary of        the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) was normalized silently (i.e. names in      ALL-CAPS were replaced by Proper-noun capitalization).</p>   <p>The unchanging parts of alternate names from the editions and translations of      Barsoum, <title>The Scattered Pearls: A History of Syriac Literature and        Sciences</title> (<ref target="http://syriaca.org/bibl/2">http://syriaca.org/bibl/2</ref>, <ref target="http://syriaca.org/bibl/3">http://syriaca.org/bibl/3</ref>, or <ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) have been supplied silently.</p>   <p>Names from the English translation of Barsoum, <title>The Scattered Pearls: A        History of Syriac Literature and Sciences</title> (<ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) were      silently transformed into sentence word order rather than the headword      alphabetization used by Barsoum. Commas were silently removed.</p>  </editorialDecl>  <classDecl>   <taxonomy>    <category xml:id="syriaca-headword">     <catDesc>The name used by Syriaca.org for document titles, citation, and          disambiguation. These names have been created according to the Syriac.org          guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc>    </category>   </taxonomy>  </classDecl> </encodingDesc>
Example
<encodingDesc>  <editorialDecl>   <p>This record has been created following the Syriaca.org editorial guidelines.      Documentation is available at: <ref target="http://syriaca.org/documentation">http://syriaca.org/documentation</ref>. <title>The Syriac Gazetteer</title>      was encoded using both the general editorial guidelines for all publications of      Syriaca.org and an encoding schema specific to <title>The Syriac        Gazetteer</title>.</p>   <p>Approximate dates described in terms of centuries or partial centuries have      been interpreted into quantitative values as documented in the Syriaca.org      guidelines for normalization of dates. See <ref target="http://syriaca.org/documentation/dates.html">Syriaca.org Guidelines        for Approximate Dates</ref>.</p>   <p>The <gi>state</gi> element of @type="existence" indicates the period for which      this place was in use as a place of its indicated type (e.g. an inhabited      settlement, a functioning monastery or church, an administrative province).      While it is possible to indicate a source for this date, this date is usually      based on the estimate of the editors and provided as an aid to searching. As a      practice, attested dates for a place based on historical sources have instead      been encoded more precisely using <gi>event</gi> of @type="attestation". Natural      features which have always existed have no date on the <gi>state</gi> element of      @type="existence" since they are are presumed to have always existed throughout      recorded history.</p>   <p>In some cases, maps from print publications have been used as the basis for      coordinate data in <title>The Syriac Gazetteer</title>. In two instances, the      editors of such print maps provided the digital coordinate data used to prepare      the print maps. Specifically, coordinates which are attributed to <title>The        Gorgias Encyclopedic Dictionary of the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) or to   <title>The Syriac World</title> (<ref target="http://syriaca.org/bibl/PUTG99V4">http://syriaca.org/bibl/PUTG99V4</ref>) were extracted from the KML files      used to create the print maps for those volumes. Because only the print maps      were published, the citation for these coordinates refers to the print source.      The editors of the <title>The Syriac Gazetteer</title> are grateful to the      editors of <title>The Gorgias Encyclopedic Dictionary of the Syriac        Heritage</title> and <title>The Syriac World</title> for providing these      coordinate files.</p>   <p>The editors have silently normalized data from other sources in some cases. The      primary instances are listed below.</p>   <p>The capitalization of names from <title>The Gorgias Encyclopedic Dictionary of        the Syriac Heritage</title> (<ref target="http://syriaca.org/bibl/1">http://syriaca.org/bibl/1</ref>) was normalized silently (i.e. names in      ALL-CAPS were replaced by Proper-noun capitalization).</p>   <p>The unchanging parts of alternate names from the editions and translations of      Barsoum, <title>The Scattered Pearls: A History of Syriac Literature and        Sciences</title> (<ref target="http://syriaca.org/bibl/2">http://syriaca.org/bibl/2</ref>, <ref target="http://syriaca.org/bibl/3">http://syriaca.org/bibl/3</ref>, or <ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) have been supplied silently.</p>   <p>Names from the English translation of Barsoum, <title>The Scattered Pearls: A        History of Syriac Literature and Sciences</title> (<ref target="http://syriaca.org/bibl/4">http://syriaca.org/bibl/4</ref>) were      silently transformed into sentence word order rather than the headword      alphabetization used by Barsoum. Commas were silently removed.</p>  </editorialDecl> ... </encodingDesc>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="editorialDecl"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="classDecl" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element encodingDesc
{
   tei_att.global.attributes,
   ( tei_editorialDecl, tei_classDecl? )
}

1.57. <entryFree>

<entryFree> (unstructured entry) contains a single unstructured entry in any kind of lexical resource, such as a dictionary or lexicon. [10.1. Dictionary Body and Overall Structure 10.2. The Structure of Dictionary Entries]
Moduledictionaries
Attributes
Member of
Contained by
textstructure: body div
May contain
Note

May contain any dictionary elements in any combination.

Example
<entryFree>  <orth>biryani</orth> or <orth>biriani</orth>  <pron>(%bIrI"A:nI)</pron>  <def>any of a variety of Indian dishes ...</def>  <etym>[from <lang>Urdu</lang>]</etym> </entryFree>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.morphLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element entryFree
{
   tei_att.global.attributes,
   tei_att.entryLike.attributes,
   tei_att.lexicographic.attributes,
   tei_att.sortable.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.entryPart
    | tei_model.morphLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
   )*
}

1.58. <event>

<event> (event) contains data relating to anything of significance that happens in time. [14.3.1. Basic Principles]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<listEvent>  <event when="1618-05-23"   xml:id="SecondDefPraguewhere="#Prague">   <eventName>1618 Defenestration of Prague</eventName>   <idno>https://www.wikidata.org/wiki/Q13365740</idno>   <listPerson type="defenstrated">    <person>     <persName>Jaroslav Bořita z Martinic</persName>     <idno type="GND">https://d-nb.info/gnd/116810998</idno>    </person>    <person>     <persName>Vilém Slavata z Chlumu a Košumberka</persName>     <idno type="GND">https://d-nb.info/gnd/1018376615</idno>    </person>    <person>     <persName>Filip Fabricius</persName>     <idno type="GND">https://d-nb.info/gnd/133946118</idno>    </person>   </listPerson>   <place xml:id="Prague">    <placeName>Prague</placeName>   </place>  </event>  <event from="1618to="1648"   xml:id="ThirtyYearsWar">   <eventName>Thirty Years’ War</eventName>   <idno>https://www.wikidata.org/wiki/Q2487</idno>   <event when="1643-03-19"    xml:id="BattleofRocroiwhere="#Rocroi">    <eventName>Battle of Rocroi</eventName>    <idno type="Wikidata">https://www.wikidata.org/wiki/Q728480</idno>    <idno type="GND">https://d-nb.info/gnd/4202901-6</idno>    <place xml:id="Rocroi">     <placeName>Rocroi</placeName>     <location>      <geo decls="#WGS">49.926111 4.522222</geo>     </location>    </place>   </event>  </event> </listEvent>
Example
<person>  <event type="matwhen="1972-10-12">   <label>matriculation</label>  </event>  <event type="gradwhen="1975-06-23">   <label>graduation</label>  </event> </person>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="idno" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.labelLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <elementRef key="eventName"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
  </alternate>
  <classRef key="model.eventLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPerson"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPlace"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <classRef key="model.objectLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element event
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.locatable.attributes,
   tei_att.naming.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   (
      tei_idno*,
      tei_model.headLike*,
      ( tei_model.pLike+ | tei_model.labelLike+ | eventName+ ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | linkGrp
       | tei_link
       | tei_idno
       | tei_ptr
      )*,
      tei_model.eventLike*,
      ( tei_model.personLike | tei_listPerson )*,
      ( tei_model.placeLike | tei_listPlace )*,
      tei_model.objectLike*,
      ( tei_relation | tei_listRelation )*
   )
}

1.59. <ex>

<ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [12.3.1.2. Abbreviation and Expansion]
Moduletranscr
Attributes
Member of
Contained by
May containCharacter data only
Example
The address is Southmoor <choice>  <expan>R<ex>oa</ex>d</expan>  <abbr>Rd</abbr> </choice>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element ex
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   tei_macro.xtext
}

1.60. <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
The address is Southmoor <choice>  <expan>Road</expan>  <abbr>Rd</abbr> </choice>
Example
<choice xml:lang="la">  <abbr>Imp</abbr>  <expan>Imp<ex>erator</ex>  </expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element expan
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.61. <explicit>

<explicit> (explicit) contains the explicit of a item, that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
core: bibl
msdescription: msItem msItemStruct
May contain
Example
<explicit>sed libera nos a malo.</explicit> <rubric>Hic explicit oratio qui dicitur dominica.</rubric> <explicit type="defective">ex materia quasi et forma sibi proporti<gap/> </explicit> <explicit type="reverse">saued be shulle that doome of day the at </explicit>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element explicit
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.msExcerpt.attributes,
   tei_macro.phraseSeq
}

1.62. <extent>

<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.7.1. Object Description]
Moduleheader
Attributes
Member of
Contained by
core: bibl
msdescription: supportDesc
May contain
Example
<extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent>
ExampleThe <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned.
<extent>  <measure unit="MiBquantity="4.2">About four megabytes</measure>  <measure unit="pagesquantity="245">245 pages of source    material</measure> </extent>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element extent { tei_att.global.attributes, tei_macro.phraseSeq }

1.63. <facsimile>

<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [12.1. Digital Facsimiles]
Moduletranscr
Attributes
Member of
Contained by
textstructure: TEI
May contain
figures: formula
textstructure: back front
Example
<facsimile>  <graphic url="page1.png"/>  <surface>   <graphic url="page2-highRes.png"/>   <graphic url="page2-lowRes.png"/>  </surface>  <graphic url="page3.png"/>  <graphic url="page4.png"/> </facsimile>
Example
<facsimile>  <surface ulx="0uly="0lrx="200lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>
Schematron
<sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone"> <sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus transcribed text should not be present within it. </sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="front" minOccurs="0"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.graphicLike"/>
   <elementRef key="surface"/>
   <elementRef key="surfaceGrp"/>
  </alternate>
  <elementRef key="back" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element facsimile
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      tei_front?,
      ( tei_model.graphicLike | tei_surface | tei_surfaceGrp )+,
      tei_back?
   )
}

1.64. <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
Note

Each <fileDesc> element contains (in order) a <titleStmt>, an <editionStmt>, a <publicationStmt>, an optional <seriesStmt>, and a <sourceDesc>.

Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="titleStmt" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="editionStmt"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="publicationStmt"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="seriesStmt"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   tei_att.global.attributes,
   (
      tei_titleStmt,
      tei_editionStmt,
      tei_publicationStmt,
      tei_seriesStmt*,
      tei_sourceDesc
   )
}

1.65. <filiation>

<filiation> (filiation) contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Example
<msContents>  <msItem>   <title>Beljakovski sbornik</title>   <filiation type="protograph">Bulgarian</filiation>   <filiation type="antigraph">Middle Bulgarian</filiation>   <filiation type="apograph">    <ref target="#DN17">Dujchev N 17</ref>   </filiation>  </msItem> </msContents> <!-- ... --> <msDesc xml:id="DN17">  <msIdentifier>   <settlement>Faraway</settlement>  </msIdentifier> <!-- ... --> </msDesc>
In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier DN17.
Example
<msItem>  <title>Guan-ben</title>  <filiation>   <p>The "Guan-ben" was widely current among mathematicians in the      Qing dynasty, and "Zhao Qimei version" was also read. It is      therefore difficult to know the correct filiation path to follow.      The study of this era is much indebted to Li Di. We explain the      outline of his conclusion here. Kong Guangsen      (1752-1786)(17) was from the same town as Dai Zhen, so he obtained      "Guan-ben" from him and studied it(18). Li Huang (d. 1811)      (19) took part in editing Si Ku Quan Shu, so he must have had      "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,      and studied "Da Yan Zong Shu Shu" (The General Dayan      Computation). He wrote Jiu Yi Suan Shu (Mathematics      Searching for One, 1803) based on this version of Shu Xue Jiu      Zhang (20).</p>   <p>One of the most important persons in restoring our knowledge      concerning the filiation of these books was Li Rui (1768(21)      -1817)(see his biography). ... only two volumes remain of this      manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,      question 2 of "Huan Tian San Ji" (square of three loops),      which later has been lost.</p>  </filiation> </msItem> <!--http://www2.nkfust.edu.tw/~jochi/ed1.htm-->
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element filiation
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_macro.specialPara
}

1.66. <finalRubric>

<finalRubric> (final rubric) contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Example
<finalRubric>Explicit le romans de la Rose ou l'art d'amours est toute enclose.</finalRubric> <finalRubric>ok lúkv ver þar Brennu-Nials savgv</finalRubric>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element finalRubric
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.msExcerpt.attributes,
   tei_macro.phraseSeq
}

1.67. <floruit>

<floruit> (floruit) contains information about a person's period of activity. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person personGrp
May contain
Example
<floruit notBefore="1066notAfter="1100"/>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element floruit
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.dimensions.attributes,
   tei_att.editLike.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.68. <foliation>

<foliation> (foliation) describes the numbering system or systems used to count the leaves or pages in a codex or similar object. [11.7.1.4. Foliation]
Modulemsdescription
Attributes
Contained by
msdescription: supportDesc
May contain
Example
<foliation>Contemporary foliation in red roman numerals in the centre of the outer margin.</foliation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element foliation { tei_att.global.attributes, tei_macro.specialPara }

1.69. <foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

Example
This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>?
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element foreign
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.70. <forename>

<forename> (forename) contains a forename, given or baptismal name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <roleName>Ex-President</roleName>  <forename>George</forename>  <surname>Bush</surname> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element forename
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.71. <formula>

<formula> (formula) contains a mathematical or other formula. [15.2. Formulæ and Mathematical Expressions]
Modulefigures
Attributes
Member of
Contained by
May contain
figures: formula
character data
Example
<formula notation="tex">$E=mc^2$</formula>
Example
<formula notation="none">E=mc<hi rend="sup">2</hi> </formula>
Example
<formula notation="mathml">  <m:math>   <m:mi>E</m:mi>   <m:mo>=</m:mo>   <m:mi>m</m:mi>   <m:msup>    <m:mrow>     <m:mi>c</m:mi>    </m:mrow>    <m:mrow>     <m:mn>2</m:mn>    </m:mrow>   </m:msup>  </m:math> </formula>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.hiLike"/>
 </alternate>
</content>
    
Schema Declaration
element formula
{
   tei_att.global.attributes,
   tei_att.notated.attributes,
   tei_att.cmc.attributes,
   ( text | tei_model.graphicLike | tei_model.hiLike )*
}

1.72. <front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
transcr: facsimile
May contain
certainty: precision
linking: link
textcrit: app witDetail
textstructure: div
Note

Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical.

Example
<front>  <epigraph>   <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla      pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί        θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>   </quote>  </epigraph>  <div type="dedication">   <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>   </p>  </div> </front>
Example
<front>  <div type="dedication">   <p>To our three selves</p>  </div>  <div type="preface">   <head>Author's Note</head>   <p>All the characters in this book are purely imaginary, and if the      author has used names that may suggest a reference to living persons      she has done so inadvertently. ...</p>  </div> </front>
Example
<front>  <div type="abstract">   <div>    <head> BACKGROUND:</head>    <p>Food insecurity can put children at greater risk of obesity because        of altered food choices and nonuniform consumption patterns.</p>   </div>   <div>    <head> OBJECTIVE:</head>    <p>We examined the association between obesity and both child-level        food insecurity and personal food insecurity in US children.</p>   </div>   <div>    <head> DESIGN:</head>    <p>Data from 9,701 participants in the National Health and Nutrition        Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.        Child-level food insecurity was assessed with the US Department of        Agriculture's Food Security Survey Module based on eight        child-specific questions. Personal food insecurity was assessed with        five additional questions. Obesity was defined, using physical        measurements, as body mass index (calculated as kg/m2) greater than        or equal to the age- and sex-specific 95th percentile of the Centers        for Disease Control and Prevention growth charts. Logistic        regressions adjusted for sex, race/ethnic group, poverty level, and        survey year were conducted to describe associations between obesity        and food insecurity.</p>   </div>   <div>    <head> RESULTS:</head>    <p>Obesity was significantly associated with personal food insecurity        for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to        2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%        CI 0.51 to 1.51). Child-level food insecurity was not associated        with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>   </div>   <div>    <head> CONCLUSIONS:</head>    <p>Personal food insecurity is associated with an increased risk of        obesity only in children aged 6 to 11 years. Personal        food-insecurity measures may give different results than aggregate        food-insecurity measures in children.</p>   </div>  </div> </front>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1" maxOccurs="1">
     <classRef key="model.div1Like"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <classRef key="model.divLike"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
   </alternate>
   <sequence minOccurs="0" maxOccurs="1">
    <classRef key="model.divBottom"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.divBottom"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element front
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      (
         tei_model.frontPart
       | tei_model.pLike
       | tei_model.pLike.front
       | tei_model.global
      )*,
      (
         (
            (
               tei_model.div1Like,
               ( tei_model.div1Like | tei_model.frontPart | tei_model.global )*
            )
          | (
               tei_model.divLike,
               ( tei_model.divLike | tei_model.frontPart | tei_model.global )*
            )
         ),
         ( tei_model.divBottom, ( tei_model.divBottom | tei_model.global )* )?
      )?
   )
}

1.73. <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
core: bibl
header: titleStmt
msdescription: msItem
May contain
Note

Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.

Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element funder
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.74. <fw>

<fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [12.6. Headers, Footers, and Similar Matter]
Moduletranscr
Attributes
typeclassifies the material encoded according to some useful typology.
Derived fromatt.typed
StatusRecommended
Datatypeteidata.enumerated
Member of
Contained by
May contain
Note

Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <fw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.

Example
<fw type="sigplace="bottom">C3</fw>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element fw
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

1.75. <gender>

<gender> (gender) specifies the gender identity of a person, persona, or character. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
valuesupplies a coded value for gender identity
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

Member of
Contained by
namesdates: person personGrp
May contain
Note

As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<gender value="W">woman</gender>
Example
<gender value="NB">non-binary</gender>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gender
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute value { list { + } }?,
   tei_macro.phraseSeq
}

1.76. <geo>

<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [14.3.4.1. Varieties of Location]
Modulenamesdates
Attributes
Member of
Contained by
May containCharacter data only
Note

Uses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

Example
<geoDecl xml:id="WGSdatum="WGS84">World Geodetic System</geoDecl> <geoDecl xml:id="OSdatum="OSGB36">Ordnance Survey</geoDecl> <!-- ... --> <location>  <desc>A tombstone plus six lines of    Anglo-Saxon text, built into the west tower (on the south side    of the archway, at 8 ft. above the ground) of the    Church of St. Mary-le-Wigford in Lincoln.</desc>  <geo decls="#WGS">53.226658 -0.541254</geo>  <geo decls="#OS">SK 97481 70947</geo> </location>
Example
<geo>41.687142 -74.870109</geo>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element geo
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.cmc.attributes,
   text
}

1.77. <gi>

<gi> (element name) contains the name (generic identifier) of an element. [23. Documentation Elements 23.5. Element Specifications]
Moduletagdocs
Attributes
schemesupplies the name of the scheme in which this name is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
this element is part of the TEI scheme.[Default]
DBK
(docbook) this element is part of the Docbook scheme.
XX
(unknown) this element is part of an unknown scheme.
Schematron
this element is from Schematron.
HTML
this element is from the HTML scheme.
Member of
Contained by
May contain
XSD Name
Example
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the <gi scheme="DBK">listItem</gi> element.</p>
This example shows the use of both a namespace prefix and the scheme attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in practice only one method should be adopted.
Content model
<content>
 <dataRef key="teidata.name"/>
</content>
    
Schema Declaration
element gi
{
   tei_att.global.attributes,
   attribute scheme { text }?,
   teidata.name
}

1.78. <handDesc>

<handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [11.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
Attributes
hands(hands) specifies the number of distinct hands identified within the manuscript
StatusOptional
Datatypeteidata.count
Member of
Contained by
msdescription: physDesc
May contain
core: p
header: handNote
msdescription: summary
Example
<handDesc>  <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote> </handDesc>
Example
<handDesc hands="2">  <p>The manuscript is written in two contemporary hands, otherwise    unknown, but clearly those of practised scribes. Hand I writes    ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably    Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand    on f. 24, but the evidence for this is insubstantial.</p> </handDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="handNote" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element handDesc
{
   tei_att.global.attributes,
   attribute hands { text }?,
   ( tei_model.pLike+ | ( tei_summary?, tei_handNote+ ) )
}

1.79. <handNote>

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader
Attributes
Contained by
msdescription: handDesc
transcr: handNotes
May contain
Example
<handNote scope="sole">  <p>Written in insular    phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed    minuscule.</p> </handNote>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element handNote
{
   tei_att.global.attributes,
   tei_att.handFeatures.attributes,
   tei_macro.specialPara
}

1.80. <handNotes>

<handNotes> contains one or more <handNote> elements documenting the different hands identified within the source texts. [12.3.2.1. Document Hands]
Moduletranscr
Attributes
Member of
Contained by
header: profileDesc
May contain
header: handNote
Example
<handNotes>  <handNote xml:id="H1script="copperplate"   medium="brown-ink">Carefully written with regular descenders</handNote>  <handNote xml:id="H2script="print"   medium="pencil">Unschooled scrawl</handNote> </handNotes>
Content model
<content>
 <elementRef key="handNote" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element handNotes { tei_att.global.attributes, tei_handNote+ }

1.81. <handShift>

<handShift> (handwriting shift) marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [12.3.2.1. Document Hands]
Moduletranscr
Attributes
newindicates a <handNote> element describing the hand concerned.
StatusRecommended
Datatypeteidata.pointer
Note

This attribute serves the same function as the hand attribute provided for those elements which are members of the att.transcriptional class. It may be renamed at a subsequent major release.

Member of
Contained by
May containEmpty element
Note

The <handShift> element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes.

Example
<l>When wolde the cat dwelle in his ynne</l> <handShift medium="greenish-ink"/> <l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element handShift
{
   tei_att.global.attributes,
   tei_att.handFeatures.attributes,
   attribute new { text }?,
   empty
}

1.82. <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="Itype="book">  <head>In the name of Christ here begins the first book of the ecclesiastical history of    Georgius Florentinus, known as Gregory, Bishop of Tours.</head>  <div2 type="section">   <head>In the name of Christ here begins Book I of the history.</head>   <p>Proposing as I do ...</p>   <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve      years passed.</p>   <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six      years from the beginning of the world down to the death of Saint Martin.</trailer>  </div2> </div1>
ExampleWhen headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
<div type="subsection">  <head place="margin">Secunda conclusio</head>  <p>   <lb n="1251"/>   <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>   </hi>   <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium    [...]  </p> </div>
ExampleThe <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">  <head>Connectives</head>  <item>above</item>  <item>accordingly</item>  <item>across from</item>  <item>adjacent to</item>  <item>again</item>  <item> <!-- ... -->  </item> </list>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element head
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   (
      text
    | lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

1.83. <height>

<height> (height) contains a measurement measured along the axis at a right angle to the bottom of the object. [11.3.4. Dimensions]
Modulemsdescription
Attributes
Member of
Contained by
May containCharacter data only
Example
<height unit="inquantity="7"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element height
{
   tei_att.global.attributes,
   tei_att.dimensions.attributes,
   tei_macro.xtext
}

1.84. <heraldry>

<heraldry> (heraldry) contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc. [11.3.8. Heraldry]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<p>Ownership stamp (xvii cent.) on i recto with the arms <heraldry>A bull passant within a bordure bezanty,    in chief a crescent for difference</heraldry> [Cole], crest, and the legend <q>Cole Deum</q>.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element heraldry { tei_att.global.attributes, tei_macro.phraseSeq }

1.85. <history>

<history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [11.8. History]
Modulemsdescription
Attributes
Contained by
msdescription: msDesc msFrag msPart
May contain
core: p
Example
<history>  <origin>   <p>Written in Durham during the mid twelfth      century.</p>  </origin>  <provenance>   <p>Recorded in two medieval      catalogues of the books belonging to Durham Priory, made in 1391 and      1405.</p>  </provenance>  <provenance>   <p>Given to W. Olleyf by William Ebchester, Prior (1446-56)      and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)      according to inscriptions on ff. 4v and 5.</p>  </provenance>  <acquisition>   <p>Presented to Trinity College in 1738 by      Thomas Gale and his son Roger.</p>  </acquisition> </history>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="origin" minOccurs="0"/>
   <elementRef key="provenance"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="acquisition"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element history
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | ( tei_summary?, tei_origin?, tei_provenance*, tei_acquisition? )
   )
}

1.86. <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader
Attributes
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
header: idno
character data
Note

<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

Example
<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat">  <g ref="#sym"/>345 </idno>
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
    
Schema Declaration
element idno
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   ( text | tei_model.gLike | tei_idno )*
}

1.87. <incipit>

<incipit> contains the incipit of a manuscript or similar object item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
core: bibl
msdescription: msItem msItemStruct
May contain
Example
<incipit>Pater noster qui es in celis</incipit> <incipit defective="true">tatem dedit hominibus alleluia.</incipit> <incipit type="biblical">Ghif ons huden onse dagelix broet</incipit> <incipit>O ongehoerde gewerdighe christi</incipit> <incipit type="lemma">Firmiter</incipit> <incipit>Ideo dicit firmiter quia ordo fidei nostre probari non potest</incipit>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element incipit
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.msExcerpt.attributes,
   tei_macro.phraseSeq
}

1.88. <institution>

<institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
Contained by
May contain
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element institution
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq.limited
}

1.89. <interpretation>

<interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
Moduleheader
Attributes
Contained by
May contain
core: p
Example
<interpretation>  <p>The part of speech analysis applied throughout section 4 was added by hand and has not    been checked</p> </interpretation>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element interpretation
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_model.pLike+
}

1.90. <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore
Attributes
Contained by
core: list
May contain
Note

May contain simple prose or a sequence of chunks.

Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n.

Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element item
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_macro.specialPara
}

1.91. <label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
ExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runontype="ordered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
ExampleLabels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">  <label>March 1757.</label>  <item>I wrote some critical observations upon Plautus.</item>  <label>March 8th.</label>  <item>I wrote a long dissertation upon some lines of Virgil.</item>  <label>June.</label>  <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus      amori.</quote>  </item>  <label>August.</label>  <item>I went to Crassy, and staid two days.</item> </list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
ExampleLabels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...] <lb/>&amp; n’entrer en mauuais &amp; mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale    entre les Romains.</label>  <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element label
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.92. <lacunaEnd>

<lacunaEnd> (lacuna end) indicates the end of a lacuna in a mostly complete textual witness. [13.1.5. Fragmentary Witnesses]
Moduletextcrit
Attributes
Member of
Contained by
textcrit: lem rdg
May containEmpty element
Example
<rdg wit="#X">  <lacunaEnd/>auctorite </rdg>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element lacunaEnd
{
   tei_att.global.attributes,
   tei_att.rdgPart.attributes,
   empty
}

1.93. <lacunaStart>

<lacunaStart> (lacuna start) indicates the beginning of a lacuna in the text of a mostly complete textual witness. [13.1.5. Fragmentary Witnesses]
Moduletextcrit
Attributes
Member of
Contained by
textcrit: lem rdg
May containEmpty element
Example
<app>  <lem wit="#El #Hg">Experience</lem>  <rdg wit="#Ha4">Ex<g ref="#per"/>   <lacunaStart/>  </rdg> </app>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element lacunaStart
{
   tei_att.global.attributes,
   tei_att.rdgPart.attributes,
   empty
}

1.94. <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
core: p
header: language
Example
<langUsage>  <language ident="fr-CAusage="60">Québecois</language>  <language ident="en-CAusage="20">Canadian business English</language>  <language ident="en-GBusage="20">British English</language> </langUsage>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="language" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element langUsage
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( tei_model.pLike+ | tei_language+ )
}

1.95. <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader
Attributes
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.
StatusRequired
Datatypeteidata.language
usagespecifies the approximate percentage of the text which uses this language.
StatusOptional
DatatypenonNegativeInteger
Contained by
header: langUsage
May contain
Note

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   tei_att.global.attributes,
   attribute ident { text },
   attribute usage { text }?,
   tei_macro.phraseSeq.limited
}

1.96. <layout>

<layout> (layout) describes how text is laid out on the page or surface of the object, including information about any ruling, pricking, or other evidence of page-preparation techniques. [11.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
Attributes
columns(columns) specifies the number of columns per page
StatusOptional
Datatype1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all pages referenced have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied. Where columns is omitted the number is assumed to be 1.

Columns may be independent of page orientation or reading direction, and a single textual stream may have one or more columns.

streams(textual streams) indicates the number of streams per page, each of which contains an independent textual stream
StatusOptional
Datatype1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all pages referenced have this number of textual streams. If two numbers are given, the number of textual streams per page varies between the values supplied. Where streams is omitted the number is assumed to be 1 and unless specified elsewhere the script orientation of the source is identical to that used in the TEI document.

ruledLines(ruled lines) specifies the number of ruled lines per column
StatusOptional
Datatype1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all columns have this number of ruled lines. If two numbers are given, the number of ruled lines per column varies between the values supplied.

writtenLines(written lines) specifies the number of written lines per column
StatusOptional
Datatype1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all columns have this number of written lines. If two numbers are given, the number of written lines per column varies between the values supplied.

Contained by
msdescription: layoutDesc
May contain
Example
<layout columns="1ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout>
Example
<layout columns="2ruledLines="42">  <p>2 columns of 42 lines ruled in ink, with central rule    between the columns.</p> </layout>
Example
<layout columns="1 2writtenLines="40 50">  <p>Some pages have 2 columns, with central rule    between the columns; each column with between 40 and 50 lines of writing.</p> </layout>
Example
<layout streams="3columns="3"/> <!-- Further down in document body --> <div type="page">  <ab>   <pb/>    一二三<cb type="top-stream"/>    一二三<cb type="mid-stream"/>    一二三<cb type="bottom-stream"/> <!-- cb here for demo purposes -->  </ab> </div>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element layout
{
   tei_att.global.attributes,
   attribute columns { list { ? } }?,
   attribute streams { list { ? } }?,
   attribute ruledLines { list { ? } }?,
   attribute writtenLines { list { ? } }?,
   tei_macro.specialPara
}

1.97. <layoutDesc>

<layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript or other object. [11.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
Attributes
Contained by
msdescription: objectDesc
May contain
core: p
msdescription: layout summary
Example
<layoutDesc>  <p>Most pages have between 25 and 32 long lines ruled in lead.</p> </layoutDesc>
Example
<layoutDesc>  <layout columns="2ruledLines="42">   <p>    <locus from="f12rto="f15v"/>      2 columns of 42 lines pricked and ruled in ink, with      central rule between the columns.</p>  </layout>  <layout columns="3">   <p>    <locus from="f16"/>Prickings for three columns are visible.</p>  </layout> </layoutDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="layout" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element layoutDesc
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_summary?, tei_layout+ ) )
}

1.98. <lem>

<lem> (lemma) contains the lemma, or base text, of a textual variation. [13.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit
Attributes
Contained by
textcrit: app rdgGrp
May contain
Note

The term lemma is used in text criticism to describe the reading given in the main text, which may be used as a heading in the apparatus itself. This usage connects it to mathematics (where a lemma is a proven proposition used as a step in a proof, a "given") and natural-language processing (where a lemma is the dictionary headword associated with an inflected form in the running text).

Example
<app>  <lem wit="#El #Hg">Experience</lem>  <rdg wit="#Latype="substantive">Experiment</rdg>  <rdg wit="#Ra2type="substantive">Eryment</rdg> </app>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.divLike"/>
  <classRef key="model.divPart"/>
  <elementRef key="titlePage"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="docAuthor"/>
  <elementRef key="docDate"/>
  <elementRef key="docEdition"/>
  <elementRef key="docImprint"/>
  <elementRef key="docTitle"/>
  <elementRef key="epigraph"/>
  <elementRef key="imprimatur"/>
  <elementRef key="titlePart"/>
  <elementRef key="epilogue"/>
  <elementRef key="performance"/>
  <elementRef key="prologue"/>
  <elementRef key="set"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
  <classRef key="model.rdgPart"/>
 </alternate>
</content>
    
Schema Declaration
element lem
{
   tei_att.global.attributes,
   tei_att.textCritical.attributes,
   tei_att.witnessed.attributes,
   (
      text
    | tei_model.divLike
    | tei_model.divPart
    | titlePage
    | argument
    | byline
    | docAuthor
    | docDate
    | docEdition
    | docImprint
    | docTitle
    | epigraph
    | imprimatur
    | titlePart
    | epilogue
    | performance
    | prologue
    | set
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
    | tei_model.rdgPart
   )*
}

1.99. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
header: availability
May contain
Note

The <license> element within the <availability> element is used to specify the Creative Commons CC-BY license under which this record is made available. Some records incorporate information from works under copyright (with permission), a fact which is also indicated in the <license> element.

Example
<license target="http://creativecommons.org/licenses/by/3.0/">  <p>Distributed under a Creative Commons Attribution 3.0 Unported License.</p> </license>
Example
<license target="http://creativecommons.org/licenses/by/3.0/">  <p>Distributed under a Creative Commons Attribution 3.0 Unported License.</p>  <p>This entry incorporates copyrighted material from the following work(s): <listBibl>    <bibl>     <ptr target="#bib78-3"/>    </bibl>    <bibl>     <ptr target="#bib78-4"/>    </bibl>    <bibl>     <ptr target="#bib78-5"/>    </bibl>   </listBibl>   <note>used under a Creative Commons Attribution license <ref target="http://creativecommons.org/licenses/by/3.0/"/>   </note>  </p> </license>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element licence
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.specialPara
}

1.100. <line>

<line> contains the transcription of a topographic line in the source document [12.2.2. Embedded Transcription]
Moduletranscr
Attributes
Member of
Contained by
transcr: line surface zone
May contain
Note

This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use <l>) nor to mark linebreaks within text which has been encoded using structural elements such as <p> (for which use <lb>).

Example
<surface>  <zone>   <line>Poem</line>   <line>As in Visions of — at</line>   <line>night —</line>   <line>All sorts of fancies running through</line>   <line>the head</line>  </zone> </surface>
Example
<surface>  <zone>   <line>Hope you enjoyed</line>   <line>Wales, as they      said</line>   <line>to Mrs FitzHerbert</line>   <line>Mama</line>  </zone>  <zone>   <line>Printed in England</line>  </zone> </surface>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.global"/>
  <classRef key="model.gLike"/>
  <classRef key="model.linePart"/>
 </alternate>
</content>
    
Schema Declaration
element line
{
   tei_att.typed.attributes,
   tei_att.global.attributes,
   tei_att.coordinated.attributes,
   tei_att.written.attributes,
   ( text | tei_model.global | tei_model.gLike | tei_model.linePart )*
}

1.102. <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Modulecore
Attributes
type(type) describes the nature of the items in the list.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Note

Previous versions of these Guidelines recommended the use of type on <list> to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.

The formal syntax of the element declarations allows <label> tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.

Member of
Contained by
May contain
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

Example
<list rend="numbered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with  <list rend="bulleted">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </item> </list>
Example
<list type="syllogismrend="bulleted">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list type="litanyrend="simple">  <item>God save us from drought.</item>  <item>God save us from pestilence.</item>  <item>God save us from wickedness in high places.</item>  <item>Praise be to God.</item> </list>
ExampleThe following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">  <head>Athelstan's Ordinance</head>  <list rend="numbered">   <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with      the stolen goods, [if he is] over twelve years and [if the value of the goods is] over      eightpence.   <list rend="numbered">     <item n="1.1">And if anyone does spare one, he is to pay for the thief with his          wergild — and the thief is to be no nearer a settlement on that account — or to          clear himself by an oath of that amount.</item>     <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is          not to be spared [whether younger or older than twelve].</item>     <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may          then be redeemed with 120 shillings; and the kindred are to stand surety for him          that he will desist for ever.</item>     <item n="1.4">And if he steals after that, they are to pay for him with his wergild,          or to bring him back there.</item>     <item n="1.5">And if he steals after that, they are to pay for him with his wergild,          whether to the king or to him to whom it rightly belongs; and everyone of those who          supported him is to pay 120 shillings to the king as a fine.</item>    </list>   </item>   <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom      no justice can be obtained, that one should order their kindred to fetch back such a      person to justice and to find him a lord in public meeting.   <list rend="numbered">     <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,          he is then to be a fugitive afterwards, and he who encounters him is to strike him          down as a thief.</item>     <item n="2.2">And he who harbours him after that, is to pay for him with his wergild          or to clear himself by an oath of that amount.</item>    </list>   </item>   <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds      his guilty man, so that the king is appealed to, is to repay the value of the goods and      120 shillings to the king; and he who appeals to the king before he demands justice as      often as he ought, is to pay the same fine as the other would have done, if he had      refused him justice.   <list rend="numbered">     <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes          known about him, is to forfeit the slave and be liable to his wergild on the first          occasionp if he does it more often, he is to be liable to pay all that he owns.</item>     <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been          an accessory of thieves who have committed theft, is to liable to the same.</item>    </list>   </item>   <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to      a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is      afterwards convicted at the three-fold ordeal.</item>  </list> </div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple">   <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have      subscribed to the pious and catholic validity of this document with the sign of the Holy      Cross.</item>   <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with      the sign of the Holy Cross.</item>   <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the      sign of the Holy Cross.</item>   <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the      sign of the Holy Cross.</item>   <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of      the Holy Cross.</item>   <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>   <item>I, Æthelwine, bishop, have subscribed through delegates.</item>   <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy      Cross.</item>  </list> </p>
Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="label"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element list
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { text }?,
   (
      ( tei_model.divTop | tei_model.global | tei_desc* )*,
      (
         ( tei_item, tei_model.global* )+
       | (
            headLabel?,
            headItem?,
            ( tei_label, tei_model.global*, tei_item, tei_model.global* )+
         )
      ),
      ( tei_model.divBottom, tei_model.global* )*
   )
}

1.103. <listApp>

<listApp> (list of apparatus entries) contains a list of apparatus entries. [13.2. Linking the Apparatus to the Text]
Moduletextcrit
Attributes
Member of
Contained by
May contain
core: desc head
textcrit: app listApp
Note

<listApp> elements would normally be located in the <back> part of a document, but they may appear elsewhere.

ExampleIn the following example from the exegetical Yasna, the base text is encoded in the <body> of the document, and two separate <listApp> elements are used in the <back>, containing variant readings written in different scripts.
<body>  <div>   <lg type="stanzaxml:id="Y-36.01"    xml:lang="pal-Avstrend="italic">    <l xml:id="Y-36.01_L-1">     <w xml:id="Y-36.01_L1_W-01">ahiiā</w>     <w xml:id="Y-36.01_L1_W-02">ϑβā</w>     <w xml:id="Y-36.01_L1_W-03">āϑrō</w>     <w xml:id="Y-36.01_L1_W-04">vərəzə̄nā</w>     <w xml:id="Y-36.01_L1_W-05">paouruiiē</w>     <w xml:id="Y-36.01_L1_W-06">pairijasāmaiδē</w>     <w xml:id="Y-36.01_L1_W-07">mazdā</w>     <w xml:id="Y-36.01_L1_W-08">ahurā</w>    </l> <!-- ... -->   </lg>  </div> </body> <!-- ... --> <back>  <div>   <listApp xml:id="CA_Y-36"    xml:lang="pal-Avst">    <head>Variants from witnesses in Avestan script</head>    <app from="#Y-36.01_L1_W-01">     <rdg wit="#Pt4 #F2 #J2 #M1">ahiiā</rdg>    </app>    <app from="#Y-36.01_L1_W-02">     <rdg wit="#Pt4 #F2 #J2 #M1">ϑβā</rdg>    </app>    <app from="#Y-36.01_L1_W-03">     <rdg wit="#Pt4 #J2 #M1">āϑrō</rdg>     <rdg wit="#F2">āϑrōi</rdg>    </app> <!-- ... -->   </listApp>   <listApp xml:id="CA_PY-36"    xml:lang="pal-Phlv">    <head>Variants from witnesses written in Pahlavi script</head>    <app from="#PY-36.01_L1_W-01">     <rdg wit="#Pt4 #F2 #J2 #M1">ʾytwnˈ</rdg>    </app>    <app from="#PY-36.01_L1_W-02">     <rdg wit="#Pt4 #F2 #J2 #M1">ʾwˈ</rdg>    </app>    <app from="#PY-36.01_L1_W-03">     <rdg wit="#Pt4 #F2 #J2 #M1">ḤNʾ</rdg>    </app> <!-- ... -->   </listApp>  </div> </back>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="app"/>
   <elementRef key="listApp"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listApp
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   ( tei_model.headLike*, tei_desc*, ( tei_app | tei_listApp )+ )
}

1.104. <listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
msdescription: msDesc
transcr: fw
Example
<listBibl>  <head>Works consulted</head>  <bibl>Blain, Clements and Grundy: Feminist Companion to    Literature in English (Yale, 1990)  </bibl>  <biblStruct>   <analytic>    <title>The Interesting story of the Children in the Wood</title>   </analytic>   <monogr>    <title>The Penny Histories</title>    <author>Victor E Neuberg</author>    <imprint>     <publisher>OUP</publisher>     <date>1968</date>    </imprint>   </monogr>  </biblStruct> </listBibl>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.milestoneLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.milestoneLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listBibl
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_model.milestoneLike | tei_relation | tei_listRelation )*,
      (
         tei_model.biblLike+,
         ( tei_model.milestoneLike | tei_relation | tei_listRelation )*
      )+
   )
}

1.105. <listPerson>

<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [14.3.2. The Person Element 16.2. Contextual Information 2.4. The Profile Description 16.3.2. Declarable Elements]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish lists of people of a particular type if convenient.

Example
<listPerson type="respondents">  <personGrp xml:id="PXXX"/>  <person xml:id="P1234sex="2age="mid"/>  <person xml:id="P4332sex="1age="mid"/>  <listRelation>   <relation type="personalname="spouse"    mutual="#P1234 #P4332"/>  </listRelation> </listPerson>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.personLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPerson"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPerson
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      (
         ( tei_model.personLike | tei_listPerson )+,
         ( tei_relation | tei_listRelation )*
      )+
   )
}

1.106. <listPlace>

<listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 14.3.4. Places]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<listPlace type="offshoreIslands">  <place>   <placeName>La roche qui pleure</placeName>  </place>  <place>   <placeName>Ile aux cerfs</placeName>  </place> </listPlace>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.placeLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPlace"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPlace
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      (
         ( tei_model.placeLike | tei_listPlace )+,
         ( tei_relation | tei_listRelation )*
      )+
   )
}

1.107. <listRelation>

<listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [14.3.2.3. Personal Relationships]
Modulenamesdates
Attributes
Member of
Contained by
May contain
core: desc head p
Note

May contain a prose description organized as paragraphs, or a sequence of <relation> elements.

Example
<listPerson>  <person xml:id="pp1"> <!-- data about person pp1 -->  </person>  <person xml:id="pp2"> <!-- data about person pp1 -->  </person> <!-- more person (pp3, pp4) elements here -->  <listRelation type="personal">   <relation name="parent"    active="#pp1 #pp2passive="#pp3 #pp4"/>   <relation name="spouse"    mutual="#pp1 #pp2"/>  </listRelation>  <listRelation type="social">   <relation name="employeractive="#pp1"    passive="#pp3 #pp5 #pp6 #pp7"/>  </listRelation> </listPerson>
The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7.
Example
<listPerson>  <person xml:id="en_pp1"> <!-- data about person en_pp1 -->  </person>  <person xml:id="en_pp2"> <!-- data about person en_pp2 -->  </person> <!-- more person (en_pp3, en_pp4) elements here --> </listPerson> <listPlace>  <place xml:id="en_pl1"> <!-- data about place en_pl1 -->  </place> <!-- more place (en_pl2, en_pl3) elements here --> </listPlace> <listRelation>  <relation name="residence"   active="#en_pp1 #en_pp2passive="#en_pl1"/> </listRelation>
The persons with identifiers en_pp1 and en_pp2 live in en_pl1.
Example
<listRelation>  <p>All speakers are members of the Ceruli family, born in Naples.</p> </listRelation>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listRelation
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_model.pLike | ( tei_relation | tei_listRelation )+ )
   )
}

1.108. <listTranspose>

<listTranspose> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks. [12.3.4.5. Transpositions]
Moduletranscr
Attributes
Member of
Contained by
May contain
core: desc
transcr: transpose
Example
<listTranspose>  <transpose>   <ptr target="#ib02"/>   <ptr target="#ib01"/>  </transpose> </listTranspose>
This example might be used for a source document which indicates in some way that the elements identified by ib02 and code ib01 should be read in that order (ib02 followed by ib01), rather than in the reading order in which they are presented in the source.
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="transpose" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element listTranspose
{
   tei_att.global.attributes,
   ( tei_desc*, tei_transpose+ )
}

1.109. <listWit>

<listWit> (witness list) lists definitions for all the witnesses referred to by a critical apparatus, optionally grouped hierarchically. [13.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit
Attributes
Member of
Contained by
May contain
core: desc head
textcrit: listWit witness
Note

May contain a series of <witness> or <listWit> elements.

The provision of a <listWit> element simplifies the automatic processing of the apparatus, e.g. the reconstruction of the readings for all witnesses from an exhaustive apparatus.

Situations commonly arise where there are many more or less fragmentary witnesses, such that there may be quite distinct groups of witnesses for different parts of a text or collection of texts. Such groups may be given separately, or nested within a single <listWit> element at the beginning of the file listing all the witnesses, partial and complete, for the text, with the attestation of fragmentary witnesses indicated within the apparatus by use of the <witStart> and <witEnd> elements described in section 13.1.5. Fragmentary Witnesses.

Note however that a given witness can only be defined once, and can therefore only appear within a single <listWit> element.

Example
<listWit>  <witness xml:id="HL26">Ellesmere, Huntingdon Library 26.C.9</witness>  <witness xml:id="PN392">Hengwrt, National Library of Wales,    Aberystwyth, Peniarth 392D</witness>  <witness xml:id="RP149">Bodleian Library Rawlinson Poetic 149    (see further <ptr target="#MSRP149"/>)</witness> </listWit>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="witness"/>
   <elementRef key="listWit"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listWit
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   ( tei_model.headLike?, tei_desc*, ( tei_witness | tei_listWit )+ )
}

1.110. <location>

<location> (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [14.3.4. Places]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<place>  <placeName>Abbey Dore</placeName>  <location>   <geo>51.969604 -2.893146</geo>  </location> </place>
Example
<place xml:id="BGbuildingtype="building">  <placeName>Brasserie Georges</placeName>  <location>   <country key="FR"/>   <settlement type="city">Lyon</settlement>   <district type="arrondissement">IIème</district>   <district type="quartier">Perrache</district>   <placeName type="street">    <num>30</num>, Cours de Verdun</placeName>  </location> </place>
Example
<place type="imaginary">  <placeName>Atlantis</placeName>  <location>   <offset>beyond</offset>   <placeName>The Pillars of <persName>Hercules</persName>   </placeName>  </location> </place>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="precision"/>
  <classRef key="model.labelLike"/>
  <classRef key="model.placeNamePart"/>
  <classRef key="model.offsetLike"/>
  <classRef key="model.measureLike"/>
  <classRef key="model.addressLike"/>
  <classRef key="model.noteLike"/>
  <classRef key="model.biblLike"/>
 </alternate>
</content>
    
Schema Declaration
element location
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      tei_precision
    | tei_model.labelLike
    | tei_model.placeNamePart
    | tei_model.offsetLike
    | tei_model.measureLike
    | tei_model.addressLike
    | tei_model.noteLike
    | tei_model.biblLike
   )*
}

1.111. <locus>

<locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [11.3.5. References to Locations within a Manuscript]
Modulemsdescription
Attributes
scheme(scheme) identifies the foliation scheme in terms of which the location is being specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
StatusOptional
Datatypeteidata.pointer
from(from) specifies the starting point of the location in a normalized form, typically a page number.
StatusOptional
Datatypeteidata.word
to(to) specifies the end-point of the location in a normalized form, typically as a page number.
StatusOptional
Datatypeteidata.word
Member of
Contained by
May contain
msdescription: locus
character data
Note

The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the ‘Ben Jonson’ example.

To associate a <locus> element with a page image or other comparable representation, the global facs attribute should be used, as shown in the ‘Birds Praise of Love’ example. The facs attribute may be used to indicate one or more image files, as in that example, or alternatively it may point to one or more appropriate XML elements, such as the <surface>, <zone>, <graphic>, or <binaryObject> elements.

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <locus from="3">p. 3ff</locus>.

Example
<!-- within ms description --><msItem n="1">  <locus target="#F1r #F1v #F2rfrom="1r"   to="2r">ff. 1r-2r</locus>  <author>Ben Jonson</author>  <title>Ode to himself</title>  <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>  <incipit>Com leaue the loathed stage</incipit>  <explicit>And see his chariot triumph ore his wayne.</explicit>  <bibl>   <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl> </msItem> <!-- within transcription ... --> <pb xml:id="F1r"/> <!-- ... --> <pb xml:id="F1v"/> <!-- ... --> <pb xml:id="F2r"/> <!-- ... -->
ExampleThe facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:
<msItem>  <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>  <title>Birds Praise of Love</title>  <bibl>   <title>IMEV</title>   <biblScope>1506</biblScope>  </bibl> </msItem>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="hi"/>
  <elementRef key="locus"/>
 </alternate>
</content>
    
Schema Declaration
element locus
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   attribute scheme { text }?,
   attribute from { text }?,
   attribute to { text }?,
   ( text | tei_model.gLike | hi | tei_locus )*
}

1.112. <locusGrp>

<locusGrp> (locus group) groups a number of locations which together form a distinct but discontinuous item within a manuscript, manuscript part, or other object. [11.3.5. References to Locations within a Manuscript]
Modulemsdescription
Attributes
scheme(scheme) identifies the foliation scheme in terms of which all the locations contained by the group are specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
msdescription: locus
Example
<msItem>  <locusGrp>   <locus from="13to="26">Bl. 13--26</locus>   <locus from="37to="58">37--58</locus>   <locus from="82to="96">82--96</locus>  </locusGrp>  <note>Stücke von Daniel Ecklin’s Reise ins h. Land</note> </msItem>
Content model
<content>
 <elementRef key="locus" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element locusGrp
{
   tei_att.global.attributes,
   attribute scheme { text }?,
   tei_locus+
}

1.113. <material>

<material> (material) contains a word or phrase describing the material of which the object being described is composed. [11.3.2. Material and Object Type]
Modulemsdescription
Attributes
functiondescribes the function or use of the material in relation to the object as a whole.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
binding
covering material of a codex
endband
sewing at the head or tail of the codex spine to strengthen the binding, often decorative
slipcase
removable protective cover for a set of one or more codices
support
the surface for writing
tie
a ribbon or string used to bind or close a codex or rolled scroll
Note

The sample values here are for descriptive bibliography. Other sets of sample values might include armrests, legs, tabletop, pan, and back for furniture; or wall, floor, window, column, ceiling, roof, stairs, chimney for architecture.

targetidentifies one or more elements to which the metamark applies.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May contain
Note

The ref attribute may be used to point to one or more items within a taxonomy of types of material, defined either internally or externally.

Example
<physDesc>  <p>   <material>Parchment</material> leaves with a  <material>sharkskin</material> binding.</p> </physDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element material
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.typed.attributes,
   attribute function { text }?,
   attribute target { list { + } }?,
   tei_macro.phraseSeq
}

1.114. <measure>

<measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures]
Modulecore
Attributes
typespecifies the type of measurement in any convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Member of
Contained by
May contain
ExampleThis example references a definition of a measurement unit declared in the TEI header:
<measure type="weight">  <num>2</num> pounds of flesh </measure> <measure type="currency">£10-11-6d</measure> <measure type="areaunitRef="#merk">2 <unit>merks</unit> of old extent</measure> <!-- In the TEI Header: --> <encodingDesc>  <unitDecl>   <unitDef xml:id="merktype="area">    <label>merk</label>    <placeName ref="#Scotland"/>    <desc>A merk was an area of land determined variably by its agricultural        productivity.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<measure quantity="40unit="hogshead"  commodity="rum">2 score hh rum</measure> <measure quantity="12unit="count"  commodity="roses">1 doz. roses</measure> <measure quantity="1unit="count"  commodity="tulips">a yellow tulip</measure>
Example
<head>Long papers.</head> <p>Speakers will be given 30 minutes each: 20 minutes for presentation, 10 minutes for discussion. Proposals should not exceed <measure max="500unit="count"   commodity="words">500    words</measure>. This presentation type is suitable for substantial research, theoretical or critical discussions.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element measure
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.measurement.attributes,
   tei_att.cmc.attributes,
   tei_att.ranging.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

1.115. <metamark>

<metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [12.3.4.2. Metamarks]
Moduletranscr
Attributes
functiondescribes the function (for example status, insertion, deletion, transposition) of the metamark.
StatusOptional
Datatypeteidata.word
targetidentifies one or more elements to which the metamark applies.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May contain
Example
<surface>  <metamark function="usedrend="line"   target="#X2"/>  <zone xml:id="zone-X2">   <line>I am that halfgrown <add>angry</add> boy, fallen asleep</line>   <line>The tears of foolish passion yet undried</line>   <line>upon my cheeks.</line> <!-- ... -->   <line>I pass through <add>the</add> travels and <del>fortunes</del> of   <retrace>thirty</retrace>   </line>   <line>years and become old,</line>   <line>Each in its due order comes and goes,</line>   <line>And thus a message for me comes.</line>   <line>The</line>  </zone>  <metamark function="used"   target="#zone-X2">Entered - Yes</metamark> </surface>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element metamark
{
   tei_att.spanning.attributes,
   tei_att.placement.attributes,
   tei_att.global.attributes,
   attribute function { text }?,
   attribute target { list { + } }?,
   tei_macro.specialPara
}

1.116. <mod>

<mod> represents any kind of modification identified within a single document. [12.3.4.1. Generic Modification]
Moduletranscr
Attributes
Member of
Contained by
May contain
Example
<mod type="subst">  <add>pleasing</add>  <del>agreable</del> </mod>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element mod
{
   tei_att.global.attributes,
   tei_att.transcriptional.attributes,
   tei_att.typed.attributes,
   tei_att.spanning.attributes,
   tei_att.dimensions.attributes,
   tei_macro.paraContent
}

1.117. <msContents>

<msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [11.6. Intellectual Content]
Modulemsdescription
Attributes
Contained by
msdescription: msDesc msFrag msPart
May contain
core: p
msdescription: msItem msItemStruct summary
Note

Unless it contains a simple prose description, this element should contain at least one of the elements <summary>, <msItem>, or <msItemStruct>. This constraint is not currently enforced by the schema.

Example
<msContents class="#sermons">  <p>A collection of Lollard sermons</p> </msContents>
Example
<msContents>  <msItem n="1">   <locus>fols. 5r-7v</locus>   <title>An ABC</title>   <bibl>    <title>IMEV</title>    <biblScope>239</biblScope>   </bibl>  </msItem>  <msItem n="2">   <locus>fols. 7v-8v</locus>   <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>   <bibl>    <title>IMEV</title>    <biblScope>3747</biblScope>   </bibl>  </msItem>  <msItem n="3">   <locus>fol. 8v</locus>   <title>Truth</title>   <bibl>    <title>IMEV</title>    <biblScope>809</biblScope>   </bibl>  </msItem>  <msItem n="4">   <locus>fols. 8v-10v</locus>   <title>Birds Praise of Love</title>   <bibl>    <title>IMEV</title>    <biblScope>1506</biblScope>   </bibl>  </msItem>  <msItem n="5">   <locus>fols. 10v-11v</locus>   <title xml:lang="la">De amico ad amicam</title>   <title xml:lang="la">Responcio</title>   <bibl>    <title>IMEV</title>    <biblScope>16 &amp; 19</biblScope>   </bibl>  </msItem>  <msItem n="6">   <locus>fols. 14r-126v</locus>   <title>Troilus and Criseyde</title>   <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>  </msItem> </msContents>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="textLang" minOccurs="0"/>
   <elementRef key="titlePage"
    minOccurs="0"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msItem"/>
    <elementRef key="msItemStruct"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element msContents
{
   tei_att.global.attributes,
   tei_att.msExcerpt.attributes,
   tei_att.msClass.attributes,
   (
      tei_model.pLike+
    | (
         tei_summary?,
         textLang?,
         titlePage?,
         ( tei_msItem | tei_msItemStruct )*
      )
   )
}

1.118. <msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [11.1. Overview]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Note

Although the <msDesc> has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable.

Example
<msDesc>  <msIdentifier>   <settlement>Oxford</settlement>   <repository>Bodleian Library</repository>   <idno type="Bod">MS Poet. Rawl. D. 169.</idno>  </msIdentifier>  <msContents>   <msItem>    <author>Geoffrey Chaucer</author>    <title>The Canterbury Tales</title>   </msItem>  </msContents>  <physDesc>   <objectDesc>    <p>A parchment codex of 136 folios, measuring approx        28 by 19 inches, and containing 24 quires.</p>    <p>The pages are margined and ruled throughout.</p>    <p>Four hands have been identified in the manuscript: the first 44        folios being written in two cursive anglicana scripts, while the        remainder is for the most part in a mixed secretary hand.</p>   </objectDesc>  </physDesc> </msDesc>
Schematron
<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional"> <sch:let name="gi" value="name(.)"/> <sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>. </sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
    <elementRef key="msPart"/>
    <elementRef key="msFrag"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msDesc
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   tei_att.docStatus.attributes,
   (
      tei_msIdentifier,
      tei_model.headLike*,
      (
         tei_model.pLike+
       | (
            tei_msContents
          | tei_physDesc
          | tei_history
          | tei_additional
          | tei_msPart
          | tei_msFrag
         )*
      )
   )
}

1.119. <msFrag>

<msFrag> (manuscript fragment) contains information about a fragment described in relation to a prior context, typically as a description of a virtual reconstruction of a manuscript or other object whose fragments were catalogued separately [11.11. Manuscript Fragments]
Modulemsdescription
Attributes
Contained by
msdescription: msDesc
May contain
Example
<msDesc>  <msIdentifier>   <msName xml:lang="la">Codex Suprasliensis</msName>  </msIdentifier>  <msFrag>   <msIdentifier>    <settlement>Ljubljana</settlement>    <repository>Narodna in univerzitetna knjiznica</repository>    <idno>MS Kopitar 2</idno>   </msIdentifier>   <msContents>    <summary>Contains ff. 10 to 42 only</summary>   </msContents>  </msFrag>  <msFrag>   <msIdentifier>    <settlement>Warszawa</settlement>    <repository>Biblioteka Narodowa</repository>    <idno>BO 3.201</idno>   </msIdentifier>  </msFrag>  <msFrag>   <msIdentifier>    <settlement>Sankt-Peterburg</settlement>    <repository>Rossiiskaia natsional'naia biblioteka</repository>    <idno>Q.p.I.72</idno>   </msIdentifier>  </msFrag> </msDesc>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="altIdentifier"/>
   <elementRef key="msIdentifier"/>
  </alternate>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msFrag
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   (
      ( tei_altIdentifier | tei_msIdentifier ),
      tei_model.headLike*,
      (
         tei_model.pLike+
       | ( tei_msContents | tei_physDesc | tei_history | tei_additional )*
      )
   )
}

1.120. <msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
Member of
Contained by
core: bibl
msdescription: msDesc msFrag msPart
May contain
Example
<msIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </msIdentifier>
Schematron
<sch:rule context="tei:msIdentifier"> <sch:report test="not( parent::tei:msPart ) and ( child::*[1]/self::idno or child::*[1]/self::altIdentifier or normalize-space(.) eq '')">An msIdentifier must contain either a repository or location.</sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.placeNamePart"
    expand="sequenceOptional"/>
   <elementRef key="institution"
    minOccurs="0"/>
   <elementRef key="repository"
    minOccurs="0"/>
   <elementRef key="collection"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="idno" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="msName"/>
   <elementRef key="objectName"/>
   <elementRef key="altIdentifier"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msIdentifier
{
   tei_att.global.attributes,
   (
      (
         tei_placeName?,
         tei_bloc?,
         tei_country?,
         tei_region?,
         tei_settlement?,
         tei_district?,
         tei_institution?,
         tei_repository?,
         tei_collection*,
         tei_idno*
      ),
      ( tei_msName | objectName | tei_altIdentifier )*
   )
}

1.121. <msItem>

<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: msContents msItem
May contain
Example
<msItem class="#saga">  <locus>ff. 1r-24v</locus>  <title>Agrip af Noregs konunga sögum</title>  <incipit>regi oc h<ex>ann</ex> setiho  <gap reason="illegibleextent="7"/>sc    heim se<ex>m</ex> þio</incipit>  <explicit>h<ex>on</ex> hev<ex>er</ex>   <ex>oc</ex>þa buit hesta .ij. aNan viþ    fé enh<ex>on</ex>o<ex>m</ex> aNan til    reiþ<ex>ar</ex>  </explicit>  <textLang mainLang="non">Old Norse/Icelandic</textLang> </msItem>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="locus"/>
   <elementRef key="locusGrp"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.titlepagePart"/>
    <classRef key="model.msItemPart"/>
    <classRef key="model.global"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msItem
{
   tei_att.global.attributes,
   tei_att.msExcerpt.attributes,
   tei_att.msClass.attributes,
   (
      ( tei_locus | tei_locusGrp )*,
      (
         tei_model.pLike+
       | ( tei_model.titlepagePart | tei_model.msItemPart | tei_model.global )+
      )
   )
}

1.122. <msItemStruct>

<msItemStruct> (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<msItemStruct n="2defective="false"  class="#biblComm">  <locus from="24vto="97v">24v-97v</locus>  <author>Apringius de Beja</author>  <title type="uniformxml:lang="la">Tractatus in Apocalypsin</title>  <rubric>Incipit Trac<supplied reason="omitted">ta</supplied>tus    in apoka<lb/>lipsin eruditissimi uiri <lb/> Apringi ep<ex>iscop</ex>i    Pacensis eccl<ex>esi</ex>e</rubric>  <finalRubric>EXPLIC<ex>IT</ex> EXPO<lb/>SITIO APOCALIPSIS    QVA<ex>M</ex> EXPOSVIT DOM<lb/>NVS APRINGIUS EP<ex>ISCOPU</ex>S.    DEO GR<ex>ACI</ex>AS AGO. FI<lb/>NITO LABORE ISTO.</finalRubric>  <bibl>   <ref target="http://amiBibl.xml#Apringius1900">Apringius</ref>, ed. Férotin</bibl>  <textLang mainLang="la">Latin</textLang> </msItemStruct>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0" maxOccurs="1">
   <elementRef key="locus"/>
   <elementRef key="locusGrp"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="author" minOccurs="0"
     maxOccurs="unbounded"/>
    <elementRef key="respStmt"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="title" minOccurs="0"
     maxOccurs="unbounded"/>
    <elementRef key="rubric" minOccurs="0"/>
    <elementRef key="incipit" minOccurs="0"/>
    <elementRef key="msItemStruct"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="explicit"
     minOccurs="0"/>
    <elementRef key="finalRubric"
     minOccurs="0"/>
    <elementRef key="colophon"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="decoNote"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="listBibl"
     minOccurs="0" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="bibl"/>
     <elementRef key="biblStruct"/>
    </alternate>
    <elementRef key="filiation"
     minOccurs="0"/>
    <classRef key="model.noteLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="textLang"
     minOccurs="0"/>
   </sequence>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msItemStruct
{
   tei_att.global.attributes,
   tei_att.msExcerpt.attributes,
   tei_att.msClass.attributes,
   (
      ( tei_locus | tei_locusGrp )?,
      (
         tei_model.pLike+
       | (
            tei_author*,
            tei_respStmt*,
            tei_title*,
            tei_rubric?,
            tei_incipit?,
            tei_msItemStruct*,
            tei_explicit?,
            tei_finalRubric?,
            tei_colophon*,
            tei_decoNote*,
            tei_listBibl*,
            ( tei_bibl | biblStruct )*,
            tei_filiation?,
            tei_model.noteLike*,
            textLang?
         )
      )
   )
}

1.123. <msName>

<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
Contained by
msdescription: msIdentifier
May contain
core: name rs
character data
Example
<msName>The Vercelli Book</msName>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="rs"/>
  <elementRef key="name"/>
 </alternate>
</content>
    
Schema Declaration
element msName
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   ( text | tei_model.gLike | tei_rs | tei_name )*
}

1.124. <msPart>

<msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript. [11.10. Manuscript Parts]
Modulemsdescription
Attributes
Contained by
msdescription: msDesc msPart
May contain
Note

As this last example shows, for compatibility reasons the identifier of a manuscript part may be supplied as a simple <altIdentifier> rather than using the more structured <msIdentifier> element. This usage is however deprecated.

Example
<msPart>  <msIdentifier>   <idno>A</idno>   <altIdentifier type="catalog">    <collection>Becker</collection>    <idno>48, Nr. 145</idno>   </altIdentifier>   <altIdentifier type="catalog">    <collection>Wiener Liste</collection>    <idno>4°5</idno>   </altIdentifier>  </msIdentifier>  <head>   <title xml:lang="la">Gregorius: Homiliae in Ezechielem</title>   <origPlace key="tgn_7008085">Weissenburg (?)</origPlace>   <origDate notBefore="0801"    notAfter="0815">IX. Jh., Anfang</origDate>  </head> </msPart>
Example
<msDesc>  <msIdentifier>   <settlement>Amiens</settlement>   <repository>Bibliothèque Municipale</repository>   <idno>MS 3</idno>   <msName>Maurdramnus Bible</msName>  </msIdentifier>  <msContents>   <summary>    <list>     <item xml:lang="en">Miscellany of various texts;</item>     <item xml:lang="la">Prudentius, Psychomachia;</item>     <item xml:lang="la">Physiologus de natura animantium</item>    </list>   </summary>   <textLang mainLang="la">Latin</textLang>  </msContents>  <physDesc>   <objectDesc form="composite_manuscript"/>  </physDesc>  <msPart>   <msIdentifier>    <idno>ms. 10066-77 ff. 140r-156v</idno>   </msIdentifier>   <msContents>    <summary xml:lang="la">Physiologus</summary>    <textLang mainLang="la">Latin</textLang>   </msContents>  </msPart>  <msPart>   <msIdentifier>    <altIdentifier>     <idno>MS 6</idno>    </altIdentifier>   </msIdentifier> <!-- other information specific to this part here -->  </msPart> <!-- more parts here --> </msDesc>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
    <elementRef key="msPart"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msPart
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   (
      tei_msIdentifier,
      tei_model.headLike*,
      (
         tei_model.pLike+
       | (
            tei_msContents
          | tei_physDesc
          | tei_history
          | tei_additional
          | tei_msPart
         )*
      )
   )
}

1.125. <musicNotation>

<musicNotation> (music notation) contains description of type of musical notation. [11.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
Example
<musicNotation>  <p>Square notation of 4-line red staves.</p> </musicNotation>
Example
<musicNotation>Neumes in <term>campo aperto</term> of the St. Gall type. </musicNotation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element musicNotation { tei_att.global.attributes, tei_macro.specialPara }

1.126. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="personref="#HOC001">Occleve</name>
Schematron
<sch:rule context="//tei:teiHeader//tei:name"> <sch:assert test="./@ref">A @ref attribute is required on the <name> element inside <teiHeader>.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.127. <note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries]
Modulecore
Attributes
typeDescribes the function of the note. This attribute is recommended and determines how the note is displayed on the page.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
abstract
A note that contains an abstract for an authority file.
corrigenda
A note describing how the record should be corrected or read differently.
deprecation
A note logging the reason(s) for deprecating a particular data point.
description
A note describing this entity (person, place, work, etc.).
disambiguation
A note disambiguating this entity from another entity in a different dataset, i.e. one without a Syriaca.org URI.
discursive
A discursive note discussing a bibliographic item related to this entity.
errata
A note describing data that is included in the record but is known to be incorrect.
incerta
A note describing uncertain data in the record.
license
A note describing the license under which this file is released.
misc
A note that cannot be categorized as any other type.
Member of
Contained by
May contain
Note

The <note> element is used for a variety of notes about the entity described in the data. All <note> elements must have an xml:lang attribute that facilitates the display of notes by language in The Srophé Application. A type attribute is required and determines how the note is displayed on the page. Available values for this type attribute are: corrigenda, deprecation, disambiguation, errata, incerta license, and misc. Only certain values are allowed in certain contexts within the document.

ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottomtype="gloss"  resp="#MDMH">  <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH">  <resp>translation from German to English</resp>  <name>Hottinger, Marie Donald Mackie</name> </respStmt>
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
ExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
Schematron
<sch:rule context="//tei:body//tei:note"> <sch:assert test="./@xml:lang"> All <note> elements in the <body> must have an @xml:lang attribute. </sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element note
{
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.written.attributes,
   tei_att.anchoring.attributes,
   tei_att.cmc.attributes,
   attribute type
   {
      "abstract"
    | "corrigenda"
    | "deprecation"
    | "description"
    | "disambiguation"
    | "discursive"
    | "errata"
    | "incerta"
    | "license"
    | "misc"
   },
   tei_macro.specialPara
}

1.128. <objectDesc>

<objectDesc> (object description) contains a description of the physical components making up the object which is being described. [11.7.1. Object Description]
Modulemsdescription
Attributes
form(form) a short project-specific name identifying the physical form of the carrier, for example as a codex, roll, fragment, partial leaf, cutting etc.
StatusOptional
Datatypeteidata.enumerated
Note

Definitions for the terms used may typically be provided by a <valList> element in the project schema specification.

Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: layoutDesc supportDesc
Example
<objectDesc form="codex">  <supportDesc material="mixed">   <p>Early modern   <material>parchment</material> and   <material>paper</material>.</p>  </supportDesc>  <layoutDesc>   <layout ruledLines="25 32"/>  </layoutDesc> </objectDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="supportDesc"
    minOccurs="0"/>
   <elementRef key="layoutDesc"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element objectDesc
{
   tei_att.global.attributes,
   attribute form { text }?,
   ( tei_model.pLike+ | ( tei_supportDesc?, tei_layoutDesc? ) )
}

1.129. <objectType>

<objectType> (object type) contains a word or phrase describing the type of object being referred to. [11.3.2. Material and Object Type]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Note

The ref attribute may be used to point to one or more items within a taxonomy of types of object, defined either internally or externally.

Example
<physDesc>  <p> Paper and vellum <objectType>codex</objectType> in modern cloth binding.</p> </physDesc>
Example
<physDesc>  <p>Fragment of a re-used marble <objectType>funerary stele</objectType>.  </p> </physDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element objectType
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq
}

1.130. <occupation>

<occupation> (occupation) contains an informal description of a person's trade, profession or occupation. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
schemeindicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource.
StatusOptional
Datatypeteidata.pointer
codeidentifies an occupation code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
namesdates: person personGrp
May contain
Note

The content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification.

Example
<occupation>accountant</occupation>
Example
<occupation scheme="#occupationtaxonomy"  code="#acc">accountant</occupation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element occupation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute scheme { text }?,
   attribute code { text }?,
   tei_macro.specialPara
}

1.131. <offset>

<offset> (offset) marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or times involved in the expression. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName key="NRPA1">  <offset>50 metres below the summit of</offset>  <geogName>   <geogFeat>Mount</geogFeat>   <name>Sinai</name>  </geogName> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element offset
{
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.132. <orgName>

<orgName> (organization name) contains an organizational name. [14.2.2. Organizational Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.133. <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l>
ExampleMore usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>   <orig>meere</orig>   <reg>mere</reg>  </choice> confusion</l> <l>And hardly shall we all be <choice>   <orig>vnderstoode</orig>   <reg>understood</reg>  </choice> </l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element orig
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.134. <origDate>

<origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript, manuscript part, or other object. [11.3.1. Origination]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<origDate notBefore="-0300"  notAfter="-0200">3rd century BCE</origDate>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element origDate
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.calendarSystem.attributes,
   tei_att.dimensions.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

1.135. <origPlace>

<origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript, manuscript part, or other object. [11.3.1. Origination]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing.

Example
<origPlace>Birmingham</origPlace>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element origPlace
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.136. <origin>

<origin> (origin) contains any descriptive or other information concerning the origin of a manuscript, manuscript part, or other object. [11.8. History]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
msdescription: history
May contain
Example
<origin notBefore="1802notAfter="1845"  evidence="internalresp="#AMH">Copied in <name type="origPlace">Derby</name>, probably from an old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>. </origin>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element origin
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.specialPara
}

1.137. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The <p> element is used for paragraphs of text in various contexts. In the body of a record, the <p> element must have an xml:id attribute.

Example
<event type="attestation"  xml:id="attestation2567-1when="0473"  srophe:computed-start="0473-01-01srophe:computed-end="0473-12-31"  source="#bib2567-3"    xmlns:srophe="https://srophe.app">  <p xml:lang="en">Attestation of name <foreign xml:lang="syr">ܬܠܢܫܐ</foreign> in <title>Vatican Syriac 160</title>.</p>  <link target="#name2567-2 #attestation2567-1"/> </event>
Schematron
<sch:rule context="//tei:text//tei:p"> <sch:assert test="./@xml:lang">A <p> element in the text body must have an @xml:lang attribute.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:p"> <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText | parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q | parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp | parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:p"> <sch:report test="( ancestor::tei:l or ancestor::tei:lg ) and not( ancestor::tei:floatingText | parent::tei:figure | parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element p
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.fragmentable.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.138. <path>

<path> (path) defines any line passing through two or more points within a <surface> element. [12.1. Digital Facsimiles 12.2.2. Embedded Transcription]
Moduletranscr
Attributes
pointsidentifies a line within the container or bounding box specified by the parent element by means of a series of two or more pairs of numbers, each of which gives the x,y coordinates of a point on the line.
Derived fromatt.coordinated
StatusOptional
Datatype2–∞ occurrences of teidata.point separated by whitespace
Member of
Contained by
transcr: line surface zone
May containEmpty element
Note

Although the simplest form of a path is a straight line between two points, a line with more than two points may bend at any point. The order of coordinates in points is significant, because the line follows the coordinate sequence.

To specify a closed polygon, use the <zone> element rather than the <path> element.

Example
<surface ulx="0uly="0lrx="443lry="272">  <graphic url="facs-fig3.jpg"/>  <path points="74,73 171,244"/>  <path points="71,203 173,116"/> </surface>
SchematronSince a <path>> represents a line with distinct start and end points, the last coordinate should not be the same as the first coordinate.
<sch:rule context="tei:path[@points]"> <sch:let name="firstPair"  value="tokenize( normalize-space( @points ), ' ')[1]"/> <sch:let name="lastPair"  value="tokenize( normalize-space( @points ), ' ')[last()]"/> <sch:let name="firstX"  value="xs:float( substring-before( $firstPair, ',') )"/> <sch:let name="firstY"  value="xs:float( substring-after( $firstPair, ',') )"/> <sch:let name="lastX"  value="xs:float( substring-before( $lastPair, ',') )"/> <sch:let name="lastY"  value="xs:float( substring-after( $lastPair, ',') )"/> <sch:report test="$firstX eq $lastX and $firstY eq $lastY">The first and last elements of this path are the same. To specify a closed polygon, use the zone element rather than the path element. </sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element path
{
   tei_att.global.attributes,
   tei_att.coordinated.attribute.start,
   tei_att.coordinated.attribute.ulx,
   tei_att.coordinated.attribute.uly,
   tei_att.coordinated.attribute.lrx,
   tei_att.coordinated.attribute.lry,
   tei_att.typed.attributes,
   tei_att.written.attributes,
   attribute points { list { * } }?,
   empty
}

1.139. <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [14.2.1. Personal Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<persName>  <forename>Edward</forename>  <forename>George</forename>  <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of  <placeName>Knebworth</placeName>  </roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persName
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.140. <person>

<person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [14.3.2. The Person Element 16.2.2. The Participant Description]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the person.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sexspecifies the sex of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

genderspecifies the gender of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

agespecifies an age group for the person.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

Member of
Contained by
namesdates: event listPerson
May contain
Note

May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

Example
<person sex="Fage="adult">  <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic    status B2.</p> </person>
Example
<person sex="intersexrole="god"  age="immortal">  <persName>Hermaphroditos</persName>  <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person>
Example
<person xml:id="Ovi01sex="Mrole="poet">  <persName xml:lang="en">Ovid</persName>  <persName xml:lang="la">Publius Ovidius Naso</persName>  <birth when="-0044-03-20"> 20 March 43 BC <placeName>    <settlement type="city">Sulmona</settlement>    <country key="IT">Italy</country>   </placeName>  </birth>  <death notBefore="0017notAfter="0018">17 or 18 AD <placeName>    <settlement type="city">Tomis (Constanta)</settlement>    <country key="RO">Romania</country>   </placeName>  </death> </person>
ExampleThe following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.
<person xml:id="arielgender="U">  <persName>Ariel</persName>  <note>Character in <title level="m">The Tempest</title>.</note> </person>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
   <elementRef key="ptr"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element person
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.sortable.attributes,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   (
      tei_model.pLike+
    | ( tei_model.personPart | tei_model.global | tei_ptr )*
   )
}

1.141. <personGrp>

<personGrp> (personal group) describes a group of individuals treated as a single person for analytic purposes. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
rolespecifies the role of this group of participants in the interaction.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as movement, employers, relatives, or servants, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sexspecifies the sex of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

genderspecifies the gender of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

agespecifies the age group of the participants.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sizedescribes informally the size or approximate size of the group for example by means of a number and an indication of accuracy e.g. approx 200.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
namesdates: event listPerson
May contain
Note

May contain a prose description organized as paragraphs, or any sequence of demographic elements in any combination.

The global xml:id attribute should be used to identify each speaking participant in a spoken text if the who attribute is specified on individual utterances.

Example
<personGrp xml:id="pg1role="audience"  sex="mixedsize="approx 50"/>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element personGrp
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   attribute role { text }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   attribute size { list { + } }?,
   ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
}

1.142. <physDesc>

<physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [11.7. Physical Description]
Modulemsdescription
Attributes
Contained by
msdescription: msDesc msFrag msPart
May contain
Example
<physDesc>  <objectDesc form="codex">   <supportDesc material="perg">    <support>Parchment.</support>    <extent>i + 55 leaves    <dimensions scope="alltype="leaf"      unit="inch">      <height></height>      <width>5⅜</width>     </dimensions>    </extent>   </supportDesc>   <layoutDesc>    <layout columns="2">In double columns.</layout>   </layoutDesc>  </objectDesc>  <handDesc>   <p>Written in more than one hand.</p>  </handDesc>  <decoDesc>   <p>With a few coloured capitals.</p>  </decoDesc> </physDesc>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.physDescPart"
   expand="sequenceOptional"/>
 </sequence>
</content>
    
Schema Declaration
element physDesc
{
   tei_att.global.attributes,
   (
      tei_model.pLike*,
      tei_objectDesc?,
      tei_handDesc?,
      tei_typeDesc?,
      tei_scriptDesc?,
      tei_musicNotation?,
      tei_decoDesc?,
      tei_additions?,
      tei_bindingDesc?,
      tei_sealDesc?,
      tei_accMat?
   )
}

1.143. <place>

<place> (place) contains data about a geographic location [14.3.4. Places]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: event listPlace place
May contain
Example
<place>  <country>Lithuania</country>  <country xml:lang="lt">Lietuva</country>  <place>   <settlement>Vilnius</settlement>  </place>  <place>   <settlement>Kaunas</settlement>  </place> </place>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.placeStateLike"/>
    <classRef key="model.eventLike"/>
    <elementRef key="name"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"/>
   <elementRef key="listPlace"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element place
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.editLike.attributes,
   tei_att.sortable.attributes,
   (
      tei_model.headLike*,
      (
         tei_model.pLike*
       | (
            tei_model.labelLike
          | tei_model.placeStateLike
          | tei_model.eventLike
          | tei_name
         )*
      ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | tei_idno
       | tei_ptr
       | linkGrp
       | tei_link
      )*,
      ( tei_model.placeLike | tei_listPlace )*
   )
}

1.144. <placeName>

<placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element placeName
{
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.145. <precision>

<precision> indicates the numerical accuracy or precision associated with some aspect of the text markup. [22.2. Indications of Precision]
Modulecertainty
Attributes
matchsupplies an XPath selection pattern using the syntax defined in [[undefined XSLT3]] which identifies a set of nodes, selected within the context identified by the target attribute if this is supplied, or within the context of the parent element if it is not.
Derived fromatt.scoping
StatusRequired
Datatypeteidata.xpath
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
precisioncharacterizes the precision of the element or attribute pointed to by the <precision> element.
StatusOptional
Datatypeteidata.certainty
stdDeviationsupplies a standard deviation associated with the value in question
StatusOptional
Datatypeteidata.numeric
Member of
Contained by
May contain
certainty: precision
core: desc
Note

The Srophé Application does not permit @notBefore and @notAfter on the <state> element. In the many cases where the precise beginning or ending dates are not known, the range of possible beginning dates or ending dates must be given within a <precision> element within <state>. This <precision> element will have a match attribute whose value is either "@from" or "@to" (depending on whether the beginning or ending date is uncertain). This <precision> element can take notBefore to indicate the terminus post quem and notAfter to indicate the terminus ante quem of the range of uncertainty. If, as is not uncommon, both the beginning and the end of the place’s existence are uncertain, these uncertainties should be represented by separate <precision> elements. When a <precision> element is used, the value of the from or to elements on the parent <state> should be within the range specified by the <precision> element but should be interpreted as imprecise.

Note: The dates indicated in the <precision> element(s) are used for search but the Srophé Application does not currently display them in the HTML.

Example
<state resp="http://syriaca.org"  type="existencefrom="0300to="0527"  srophe:computed-end="0527-01-01srophe:computed-start="0300-01-01"    xmlns:srophe="https://srophe.app">  <precision match="@fromnotAfter="0300"   srophe:computed-end="0300-01-01"/>  <precision match="@tonotAfter="1943"   notBefore="0527srophe:computed-end="1943-01-01"   srophe:computed-start="0527-01-01"/> </state>
Example
<state type="existencefrom="0270"  to="0694syriaca-computed-end="0694-01-01"  syriaca-computed-start="0270-01-01">  <precision match="@fromnotAfter="0270"   syriaca-computed-end="0270-01-01"/>  <precision match="@tonotAfter="1200"   notBefore="0694syriaca-computed-end="1200-01-01"   syriaca-computed-start="0694-01-01"/> </state>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element precision
{
   tei_att.global.attributes,
   tei_att.ranging.attributes,
   tei_att.datable.attributes,
   attribute match { text },
   attribute calendar { list { + } }?,
   attribute precision { text }?,
   attribute stdDeviation { text }?,
   ( tei_model.descLike | tei_model.certLike )*
}

1.146. <principal>

<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
core: bibl
header: titleStmt
msdescription: msItem
May contain
Example
<principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element principal
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.147. <profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
Note

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element profileDesc { tei_att.global.attributes, tei_model.profileDescPart* }

1.148. <provenance>

<provenance> (provenance) contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [11.8. History]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
msdescription: history
May contain
Example
<provenance>Listed as the property of Lawrence Sterne in 1788.</provenance> <provenance>Sold at Sothebys in 1899.</provenance>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element provenance
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   tei_macro.specialPara
}

1.149. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element ptr
{
   tei_att.cReferencing.attributes,
   tei_att.declaring.attributes,
   tei_att.global.attributes,
   tei_att.internetMedia.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   empty
}

1.150. <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
core: bibl
May contain
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

1.151. <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
Note

The <publicationStmt> is where we identify Syriaca.org as the entity responsible for publishing this information, indicate the date of the most recent edit, and identify the use license (Creative Commons CC-BY). The <publicationStmt> contains requires (in order) the following <authority>, <idno>, <availability>, and <date>.

Example
<publicationStmt>  <authority>Syriaca.org: The Syriac Reference Portal</authority>  <idno type="URI">http://syriaca.org/place/1027/tei</idno>  <availability>   <licence target="http://creativecommons.org/licenses/by/3.0/">    <p>Distributed under a Creative Commons Attribution 3.0 Unported License.</p>   </licence>  </availability>  <date>2014-01-14-05:00</date> </publicationStmt>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="authority" minOccurs="1"/>
  <elementRef key="idno" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="availability"
   minOccurs="1"/>
  <elementRef key="date" minOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element publicationStmt
{
   tei_att.global.attributes,
   ( tei_authority, tei_idno+, tei_availability, tei_date )
}

1.152. <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore
Attributes
Member of
Contained by
May contain
Note

If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.

Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element quote
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.msExcerpt.attributes,
   tei_att.notated.attributes,
   tei_att.cmc.attributes,
   tei_macro.specialPara
}

1.153. <rdg>

<rdg> (reading) contains a single reading within a textual variation. [13.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit
Attributes
Member of
Contained by
textcrit: app rdgGrp
May contain
Example
<rdg wit="#Ra2">Eryment</rdg>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.divLike"/>
  <classRef key="model.divPart"/>
  <elementRef key="titlePage"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="docAuthor"/>
  <elementRef key="docDate"/>
  <elementRef key="docEdition"/>
  <elementRef key="docImprint"/>
  <elementRef key="docTitle"/>
  <elementRef key="epigraph"/>
  <elementRef key="imprimatur"/>
  <elementRef key="titlePart"/>
  <elementRef key="epilogue"/>
  <elementRef key="performance"/>
  <elementRef key="prologue"/>
  <elementRef key="set"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
  <classRef key="model.rdgPart"/>
 </alternate>
</content>
    
Schema Declaration
element rdg
{
   tei_att.global.attributes,
   tei_att.textCritical.attributes,
   tei_att.witnessed.attributes,
   (
      text
    | tei_model.divLike
    | tei_model.divPart
    | titlePage
    | argument
    | byline
    | docAuthor
    | docDate
    | docEdition
    | docImprint
    | docTitle
    | epigraph
    | imprimatur
    | titlePart
    | epilogue
    | performance
    | prologue
    | set
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
    | tei_model.rdgPart
   )*
}

1.154. <rdgGrp>

<rdgGrp> (reading group) within a textual variation, groups two or more readings perceived to have a genetic relationship or other affinity. [13.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit
Attributes
Contained by
textcrit: app rdgGrp
May contain
core: note
Note

May contain readings and nested reading groups.

Usually, only one <lem> element should appear within a single apparatus entry, whether it appears outside a <rdgGrp> element or within it.

Example
<app>  <lem wit="#El #Ra2">though</lem>  <rdgGrp type="orthographic">   <rdg wit="#Hg">thogh</rdg>   <rdg wit="#La">thouhe</rdg>  </rdgGrp> </app>
Schematron
<sch:rule context="tei:rdgGrp"> <sch:assert test="count(tei:lem) lt 2">Only one <lem> element may appear within a <rdgGrp></sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="lem" minOccurs="0"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.rdgLike"/>
   <classRef key="model.noteLike"/>
   <elementRef key="witDetail"/>
   <elementRef key="wit"/>
   <elementRef key="rdgGrp"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element rdgGrp
{
   tei_att.global.attributes,
   tei_att.textCritical.attributes,
   (
      tei_lem?,
      (
         tei_model.rdgLike
       | tei_model.noteLike
       | tei_witDetail
       | tei_wit
       | tei_rdgGrp
      )*
   )
}

1.155. <recordHist>

<recordHist> (recorded history) provides information about the source and revision status of the parent manuscript or object description itself. [11.9.1. Administrative Information]
Modulemsdescription
Attributes
Contained by
msdescription: adminInfo
May contain
core: p
header: change
msdescription: source
Example
<recordHist>  <source>   <p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional research      by P.M.W.Robinson</p>  </source>  <change when="1999-06-23">   <name>LDB</name> (editor)    checked examples against DTD version 3.6  </change> </recordHist>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="source"/>
   <elementRef key="change" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element recordHist
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_source, tei_change* ) )
}

1.156. <redo>

<redo> indicates one or more cancelled interventions in a document which have subsequently been marked as reaffirmed or repeated. [12.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
Moduletranscr
Attributes
targetpoints to one or more elements representing the interventions which are being reasserted.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May containEmpty element
Example
<line>  <redo hand="#g_ttarget="#redo-1"   cause="fix"/>  <mod xml:id="redo-1rend="strikethrough"   spanTo="#anchor-1hand="#g_bl"/>Ihr hagren, triſten, krummgezog<mod rend="strikethrough">nen</mod>ener Nacken </line> <line>Wenn ihr nur piepſet iſt die Welt ſchon matt.<anchor xml:id="anchor-1"/> </line>
This encoding represents the following sequence of events:
  • "Ihr hagren, triſten, krummgezog nenener Nacken/ Wenn ihr nur piepſet iſt die Welt ſchon matt." is written
  • the redundant letters "nen" in "nenener" are deleted
  • the whole passage is deleted by hand g_bl using strikethrough
  • the deletion is reasserted by another hand (identified here as g_t)
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element redo
{
   tei_att.global.attributes,
   tei_att.spanning.attributes,
   tei_att.transcriptional.attributes,
   tei_att.dimensions.attributes,
   attribute target { list { + } }?,
   empty
}

1.157. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<sch:rule context="tei:ref"> <sch:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   tei_att.cReferencing.attributes,
   tei_att.declaring.attributes,
   tei_att.global.attributes,
   tei_att.internetMedia.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.158. <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q>
ExampleIt is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>   <reg resp="#LB">knock</reg>   <orig>cnk</orig>  </choice> if an <choice>   <reg>answer</reg>   <orig>nsr</orig>  </choice> is <choice>   <reg>required</reg>   <orig>reqd</orig>  </choice> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element reg
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.159. <region>

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <region type="staten="IL">Illinois</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element region
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.160. <relation>

<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [14.3.2.3. Personal Relationships]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
namesupplies a name for the kind of relationship of which this is an instance.
StatusOptional
Datatypeteidata.enumerated
passiveidentifies the ‘passive’ participants in a non-mutual relationship.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
activeidentifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mutualsupplies a list of participants amongst all of whom the relationship holds equally.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
core: desc
Note

Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.

Example
<relation type="socialname="supervisor"  active="#p1passive="#p2 #p3 #p4"/>
This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.
Example
<relation type="personalname="friends"  mutual="#p2 #p3 #p4"/>
This indicates that p2, p3, and p4 are all friends.
Example
<relation type="CRM"  name="P89_falls_within"  active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"  passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>
This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs.
Example
<relation resp="http://viaf.org/viaf/44335536/"  ref="http://purl.org/saws/ontology#isVariantOf"  active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"  passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>
This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).
Schematron
<sch:rule context="tei:relation"> <sch:assert test="@ref or @key or @name">One of the attributes @name, @ref or @key must be supplied</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:report test="@passive and not(@active)">the attribute @passive may be supplied only if the attribute @active is supplied</sch:report> </sch:rule>
Content model
<content>
 <elementRef key="desc" minOccurs="0"/>
</content>
    
Schema Declaration
element relation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.canonical.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute name { text }?,
   attribute passive { list { + } }?,
   ( attribute active { list { + } }? | attribute mutual { list { + } }? ),
   tei_desc?
}

1.161. <repository>

<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
Contained by
May contain
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element repository
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq.limited
}

1.162. <resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
core: respStmt
May contain
Note

The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

Example
<respStmt>  <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>  <name>Edward Child</name> </respStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element resp
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.163. <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
Member of
Contained by
core: bibl
msdescription: msItem msItemStruct
May contain
core: name resp
namesdates: orgName
Note

Both the editors and other parties who are responsible for the creation of this TEI place record are then identified individually in <respStmt> elements (<resp> stands for "responsibility"). The schema requires the record have at least one <respStmt> which would describe the contribution of the <editor> with the role="creator". Most records will have multiple <respStmt> elements, especially in cases where there were contributions made by persons who do not fall into the available @role values. The contents of the <respStmt> element are the description of the responsibility wrapped in a <resp> element followed by the name of the responsible party contained in a <name> element or the name of the responsible organization in an <orgName> element. The <name> element should take a ref attribute which points to the xml:id of the editor within the "editors.xml" document. Additional participants in the creation of the file, for example by entering Syriac or Arabic text, can be given additional <respStmt> entries.

Example
<titleStmt> ... <respStmt>   <resp>Data merging, Pleiades and Wikipedia linking, and XML by</resp>   <name ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas A.      Carlson</name>  </respStmt>  <respStmt>   <resp>Wilmshurst index information entry by</resp>   <name ref="http://syriaca.org/documentation/editors.xml#adavis">Anthony      Davis</name>  </respStmt> </titleStmt>
Example
<respStmt>  <resp>These names were received as a dataset from E-Ktobe : manuscrits syriaques    (<ref target="http://syriac.msscatalog.org/">http://syriac.msscatalog.org/</ref>). Née sur l’initiative d'André Binggeli    (IRHT-CNRS), Françoise Briquel-Chatonnet (Orient et Méditerranée-CNRS), Muriel    Debié (EPHE) et Alain Desreumaux (Orient et Méditerranée-CNRS) dans le cadre du    programme SYRAB de l'ANR (Agence Nationale de la Recherche), la base e-ktobe est    actuellement placée sous la responsabilité scientifique d’André Binggeli et Emilie    Villey (Orient et Méditerranée-CNRS). Liste des collaborateurs contribuant ou    ayant contribué à l’alimentation de la base : Youssef Dergham (Bibliothèque du    patriarcat syro-catholique de Charfet), Margherita Farina (CNRS, Paris), Simone I.    M. Pratelli (U. de Constance), Flavia Ruani (U. de Gand) et Eleonora Serra (U. de    Pise).</resp>  <orgName ref="http://syriac.msscatalog.org/">E-Ktobe : manuscrits    syriaques</orgName> </respStmt>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="resp" minOccurs="1"
   maxOccurs="1"/>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="orgName" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="name" minOccurs="1"
    maxOccurs="1"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   ( tei_resp, ( tei_orgName | tei_name ) )
}

1.164. <restore>

<restore> (restore) indicates restoration of text to an earlier state by cancellation of an editorial or authorial marking or instruction. [12.3.1.6. Cancellation of Deletions and Other Markings]
Moduletranscr
Attributes
Member of
Contained by
May contain
Note

On this element, the type attribute categorizes the way that the cancelled intervention has been indicated in some way, for example by means of a marginal note, over-inking, additional markup, etc.

Example
For I hate this <restore hand="#dhl"  type="marginalStetNote">  <del>my</del> </restore> body
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element restore
{
   tei_att.global.attributes,
   tei_att.transcriptional.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_macro.paraContent
}

1.165. <retrace>

<retrace> contains a sequence of writing which has been retraced, for example by over-inking, to clarify or fix it. [12.3.4.3. Fixation and Clarification]
Moduletranscr
Attributes
Member of
Contained by
May contain
Note

Multiple retraces are indicated by nesting one <retrace> within another. In principle, a retrace differs from a substitution in that second and subsequent rewrites do not materially alter the content of an element. Where minor changes have been made during the retracing action however these may be marked up using <del>, <add>, etc. with an appropriate value for the change attribute.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element retrace
{
   tei_att.global.attributes,
   tei_att.spanning.attributes,
   tei_att.transcriptional.attributes,
   tei_att.dimensions.attributes,
   tei_macro.paraContent
}

1.166. <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
status
StatusOptional
Legal values are:
draft
(draft) Indicates that this document is more-or-less complete but remains in draft status.
incomplete
(incomplete) Indicates that this document is incomplete.
published
(published) Indicates that this document has been published.
underReview
(under review) Indicates that this document is under review by one or more editors.
Contained by
header: teiHeader
May contain
header: change
Note

The <revisionDesc> element is used to include a detailed log of which changes have been made to this file, when, and by whom. The <revisionDesc> should have a status attribute which indicates the publication stage of the file. Possible values for this attribute include: “draft,” “incomplete,” “published,” and “underReview”. Each revision contains a <change> element.

Example
<revisionDesc status="published">  <change who="http://syriaca.org/documentation/editors.xml#wsalesky"   when="2014-06-30-04:00">CHANGED tei:author element to tei:persName under tei:event    element.</change>  <change who="http://syriaca.org/documentation/editors.xml#tcarlson"   when="2014-06-12-05:00">ADDED: Yaqut citation and attestation</change>  <change who="http://syriaca.org/documentation/editors.xml#wsalesky"   when="2014-01-14">ADDED: relation element with shares-name-with attribute for all    place headwords that share names</change>  <change who="http://syriaca.org/documentation/editors.xml#wsalesky"   when="2014-01-14">ADDED: syriaca-computed-start and syriaca-computed-end    attributes for searching</change>  <change who="http://syriaca.org/documentation/editors.xml#tcarlson"   when="2013-12-18-05:00">CREATED: place</change> </revisionDesc>
Content model
<content>
 <elementRef key="change" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element revisionDesc
{
   tei_att.global.attributes,
   attribute status { "draft" | "incomplete" | "published" | "underReview" }?,
   tei_change*
}

1.167. <roleName>

<roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

A <roleName> may be distinguished from an <addName> by virtue of the fact that, like a title, it typically exists independently of its holder.

Example
<persName>  <forename>William</forename>  <surname>Poulteny</surname>  <roleName>Earl of Bath</roleName> </persName>
Example
<p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official, including the Supreme Court justices, required by statute to be “learned in the law.”</p>
Example
<p>  <persName ref="#NJF">   <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>, representing the administration, asserted in rebuttal that there was nothing to disavow (...) <persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations alike, have repeatedly said they must honor. </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element roleName
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.168. <rs>

<rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rs
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.169. <rubric>

<rubric> (rubric) contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which a manuscript or other object signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, typically in red ink, or by use of different size or type of script, or some other such visual device. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Example
<rubric>Nu koma Skyckiu Rym<ex>ur</ex>.</rubric> <rubric>Incipit liber de consciencia humana a beatissimo Bernardo editus.</rubric> <rubric>  <locus>16. f. 28v in margin: </locus>Dicta Cassiodori </rubric>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rubric
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.msExcerpt.attributes,
   tei_macro.phraseSeq
}

1.170. <scriptDesc>

<scriptDesc> (script description) contains a description of the scripts used in a manuscript or other object. [11.7.2.1. Writing]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: summary
Example
<scriptDesc>  <p/> </scriptDesc>
Example
<scriptDesc>  <summary>Contains two distinct styles of scripts </summary>  <scriptNote xml:id="style-1">.</scriptNote>  <scriptNote xml:id="style-2">.</scriptNote> </scriptDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="scriptNote"
    minOccurs="1" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element scriptDesc
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_summary?, scriptNote+ ) )
}

1.171. <seal>

<seal> (seal) contains a description of one seal or similar applied to the object described [11.7.3.2. Seals]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
contemporary(contemporary) specifies whether or not the seal is contemporary with the item to which it is affixed
StatusOptional
Datatypeteidata.xTruthValue
Contained by
msdescription: sealDesc
May contain
core: p
msdescription: decoNote
Example
<seal n="2type="pendant"  subtype="cauda_duplex">  <p>The seal of <name>Jens Olufsen</name> in black wax.    (<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.    Parchment tag on which is written: <q>Woldorp Iohanne G</q>.</p> </seal>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <elementRef key="decoNote"/>
 </alternate>
</content>
    
Schema Declaration
element seal
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   attribute contemporary { text }?,
   ( tei_model.pLike | tei_decoNote )+
}

1.172. <sealDesc>

<sealDesc> (seal description) describes the seals or similar items related to the object described, either as a series of paragraphs or as a series of <seal> elements. [11.7.3.2. Seals]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
core: p
Example
<sealDesc>  <seal type="pendantcontemporary="true">   <p>Green wax vertical oval seal attached at base.</p>  </seal> </sealDesc>
Example
<sealDesc>  <p>Parchment strip for seal in place; seal missing.</p> </sealDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="decoNote"/>
    <elementRef key="seal"/>
    <elementRef key="condition"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element sealDesc
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | ( tei_summary?, ( tei_decoNote | tei_seal | tei_condition )+ )
   )
}

1.173. <secFol>

<secFol> (second folio) marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. [11.3.7. Catchwords, Signatures, Secundo Folio]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<secFol>(con-)versio morum</secFol>
Schematron
<sch:rule context="tei:secFol"> <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element secFol { tei_att.global.attributes, tei_macro.phraseSeq }

1.174. <secl>

<secl> (secluded text) Secluded. Marks text present in the source which the editor believes to be genuine but out of its original place (which is unknown). [12.3.1.7. Text Omitted from or Supplied in the Transcription]
Moduletranscr
Attributes
reasonone or more words indicating why this text has been secluded, e.g. interpolated etc.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
Example
<rdg source="#Pescani">  <secl>   <l n="15xml:id="l15">Alphesiboea suos ulta est pro coniuge fratres,</l>   <l n="16xml:id="l16">sanguinis et cari vincula rupit amor.</l>  </secl> </rdg> <note>secl. Pescani</note>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element secl
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   attribute reason { list { + } }?,
   tei_macro.paraContent
}

1.175. <seriesStmt>

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
Example
<seriesStmt>  <title>Machine-Readable Texts for the Study of Indian Literature</title>  <respStmt>   <resp>ed. by</resp>   <name>Jan Gonda</name>  </respStmt>  <biblScope unit="volume">1.2</biblScope>  <idno type="ISSN">0 345 6789</idno> </seriesStmt>
Content model
<content>
 <sequence minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="title" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="editor" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="respStmt" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="idno" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="biblScope" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element seriesStmt
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( tei_title, tei_editor+, tei_respStmt*, tei_idno, tei_biblScope* )*
}

1.176. <settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element settlement
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.177. <sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Modulecore
Attributes
Member of
Contained by
May contain
Example
for his nose was as sharp as a pen, and <sic>a Table</sic> of green fields.
ExampleIf all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as a pen, and <choice>  <sic>a Table</sic>  <corr>a' babbld</corr> </choice> of green fields.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element sic
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.178. <signatures>

<signatures> (signatures) contains discussion of the leaf or quire signatures found within a codex or similar object. [11.3.7. Catchwords, Signatures, Secundo Folio]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<signatures>Quire and leaf signatures in letters, [b]-v, and roman numerals; those in quires 10 (1) and 17 (s) in red ink and different from others; every third quire also signed with red crayon in arabic numerals in the center lower margin of the first leaf recto: "2" for quire 4 (f. 19), "3" for quire 7 (f. 43); "4," barely visible, for quire 10 (f. 65), "5," in a later hand, for quire 13 (f. 89), "6," in a later hand, for quire 16 (f. 113).</signatures>
Schematron
<sch:rule context="tei:signatures"> <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element signatures { tei_att.global.attributes, tei_macro.specialPara }

1.179. <source>

<source> (source) describes the original source for the information contained with a manuscript or object description. [11.9.1.1. Record History]
Modulemsdescription
Attributes
Contained by
msdescription: recordHist
May contain
Example
<source>Derived from <ref>Stanley (1960)</ref> </source>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element source { tei_att.global.attributes, tei_macro.specialPara }

1.180. <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
core: p
msdescription: msDesc
Note

The <sourceDesc> element is a mandatory component of the <fileDesc> element. Its purpose is to indicate the source of the text which is encoded in this file, for library cataloging among other uses. For Syriaca.org data that is not marking up text from a source, the option of indicating that this TEI is "born digital," should be used. For text encoding projects

Example
<sourceDesc xml:id="sourceDesc1">  <biblStruct>   <monogr>    <editor>     <forename>G. H.</forename>     <surname>Gwilliam</surname>    </editor>    <editor>     <forename>J.</forename>     <surname>Pinkerton</surname>    </editor>    <editor>     <forename>John</forename>     <surname>Gwynn</surname>    </editor>    <title level="m">The New Testament in Syriac [<foreign xml:lang="syr">ܕܝܬܝܩܐ          ܚܕܬܐ ܕܡܪܢ ܝܫܘܥ ܡܫܝܚܐ</foreign>]</title>    <idno type="URI">http://syriaca.org/bibl/2491</idno>    <idno type="zotero">1049</idno>    <idno type="URI">http://zotero.org/groups/392292/items/N4KFR4M9</idno>    <ref target="https://archive.org/details/newtestamentinsy00lond"/>    <imprint>     <pubPlace>London</pubPlace>     <publisher>British and Foreign Bible Society</publisher>     <date>1905</date>    </imprint>   </monogr>  </biblStruct> </sourceDesc>
Example
<sourceDesc>  <biblStruct>   <monogr>    <title level="m">Gorgias Encyclopedic Dictionary of the Syriac Heritage</title>    <editor>Sebastian P. Brock</editor>    <editor>Aaron M. Butts</editor>    <editor>George A. Kiraz</editor>    <editor>Lucas Van Rompay</editor>    <imprint>     <pubPlace>Piscataway, N.J.</pubPlace>     <publisher>Gorgias Press for Beth Mardutho: The Syriac Institute</publisher>     <date>2011</date>     <note>Copyright ©2011 by Beth Mardutho: The Syriac Institute</note>     <note>ISBN: 978-1-59333-714-8</note>    </imprint>   </monogr>  </biblStruct> </sourceDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <elementRef key="biblStruct"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="msDesc" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="p" minOccurs="1"
   maxOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element sourceDesc
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( biblStruct | tei_msDesc | tei_p )
}

1.181. <sourceDoc>

<sourceDoc> contains a transcription or other representation of a single source document potentially forming part of a dossier génétique or collection of sources. [12.1. Digital Facsimiles 12.2.2. Embedded Transcription]
Moduletranscr
Attributes
Member of
Contained by
textstructure: TEI
May contain
Note

This element may be used as an alternative to <facsimile> for TEI documents containing only page images, or for documents containing both images and transcriptions. Transcriptions may be provided within the <surface> elements making up a source document, in parallel with them as part of a <text> element, or in both places if the encoder wishes to distinguish these two modes of transcription.

Example
<sourceDoc>  <surfaceGrp n="leaf1">   <surface facs="page1.png">    <zone>All the writing on page 1</zone>   </surface>   <surface>    <graphic url="page2-highRes.png"/>    <graphic url="page2-lowRes.png"/>    <zone>     <line>A line of writing on page 2</line>     <line>Another line of writing on page 2</line>    </zone>   </surface>  </surfaceGrp> </sourceDoc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <elementRef key="surface"/>
  <elementRef key="surfaceGrp"/>
 </alternate>
</content>
    
Schema Declaration
element sourceDoc
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   ( tei_model.global | tei_model.graphicLike | tei_surface | tei_surfaceGrp )+
}

1.182. <space>

<space> (space) indicates the location of a significant space in the text. [12.4.1. Space]
Moduletranscr
Attributes
resp(responsible party) (responsible party) indicates the individual responsible for identifying and measuring the space
Derived fromatt.global.responsibility
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
dim(dimension) indicates whether the space is horizontal or vertical.
StatusRecommended
Datatypeteidata.enumerated
Legal values are:
horizontal
the space is horizontal.
vertical
the space is vertical.
Note

For irregular shapes in two dimensions, the value for this attribute should reflect the more important of the two dimensions. In conventional left-right scripts, a space with both vertical and horizontal components should be classed as vertical.

Member of
Contained by
May contain
certainty: precision
core: desc
Note

This element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like.

Example
By god if wommen had writen storyes As <space quantity="7unit="minims"/> han within her oratoryes
Example
στρατηλάτ<space quantity="1unit="chars"/>ου
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element space
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.rendition.attribute.style,
   tei_att.global.rendition.attribute.rendition,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.facs.attribute.facs,
   tei_att.global.change.attribute.change,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.source.attribute.source,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   attribute resp { list { + } }?,
   attribute dim { "horizontal" | "vertical" }?,
   ( tei_model.descLike | tei_model.certLike )*
}

1.183. <sponsor>

<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
core: bibl
header: titleStmt
msdescription: msItem
May contain
Note

Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element <funder>), who provide the funding but do not necessarily take intellectual responsibility.

Example
<sponsor>Association for Computers and the Humanities</sponsor> <sponsor>Association for Computational Linguistics</sponsor> <sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element sponsor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.184. <stamp>

<stamp> (stamp) contains a word or phrase describing a stamp or similar device. [11.3.3. Watermarks and Stamps]
Modulemsdescription
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/> SI NON LICET<lb/> NOBIS RO<lb/> manii imperii <stamp>Bodleian stamp</stamp>  <lb/> </rubric>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element stamp
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.185. <state>

<state> (state) contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [14.3.1. Basic Principles 14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
certainty: precision
msdescription: msDesc
namesdates: state
Note

Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<state ref="#SCHOLtype="status">  <label>scholar</label> </state>
Example
<org>  <orgName notAfter="1960">The Silver Beetles</orgName>  <orgName notBefore="1960">The Beatles</orgName>  <state type="membershipfrom="1960-08"   to="1962-05">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Stuart Sutcliffe</persName>    <persName>Pete Best</persName>   </desc>  </state>  <state type="membershipnotBefore="1963">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Ringo Starr</persName>   </desc>  </state> </org>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="state" minOccurs="1"
    maxOccurs="unbounded"/>
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.headLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element state
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.naming.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      tei_precision*,
      (
         tei_state+
       | (
            tei_model.headLike*,
            tei_model.pLike+,
            ( tei_model.noteLike | tei_model.biblLike )*
         )
       | ( tei_model.labelLike | tei_model.noteLike | tei_model.biblLike )*
      )
   )
}

1.186. <subst>

<subst> (substitution) groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text. [12.3.1.5. Substitutions]
Moduletranscr
Attributes
Member of
Contained by
May contain
transcr: fw surplus
Example
... are all included. <del hand="#RG">It is</del> <subst>  <add>T</add>  <del>t</del> </subst>he expressed
Example
that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>  <del>very</del>  <lb/>  <add>principally</add> </subst> remembered in her Will.
Example
<ab>τ<subst>   <add place="above">ῶν</add>   <del>α</del>  </subst> συνκυρόντ<subst>   <add place="above">ων</add>   <del>α</del>  </subst> ἐργαστηρί<subst>   <add place="above">ων</add>   <del>α</del>  </subst> </ab>
Example
<subst>  <del>   <gap reason="illegiblequantity="5"    unit="character"/>  </del>  <add>apple</add> </subst>
Schematron
<sch:rule context="tei:subst"> <sch:assert test="child::tei:add and (child::tei:del or child::tei:surplus)">  <sch:name/> must have at least one child add and at least one child del or surplus</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <elementRef key="add"/>
  <elementRef key="surplus"/>
  <elementRef key="del"/>
  <classRef key="model.milestoneLike"/>
 </alternate>
</content>
    
Schema Declaration
element subst
{
   tei_att.global.attributes,
   tei_att.transcriptional.attributes,
   tei_att.dimensions.attributes,
   ( add | tei_surplus | del | tei_model.milestoneLike )+
}

1.187. <substJoin>

<substJoin> (substitution join) identifies a series of possibly fragmented additions, deletions, or other revisions on a manuscript that combine to make up a single intervention in the text [12.3.1.5. Substitutions]
Moduletranscr
Attributes
Member of
Contained by
May contain
certainty: precision
core: desc
Example
While <del xml:id="r112">pondering</del> thus <add xml:id="r113">she mus'd</add>, her pinions fann'd <substJoin target="#r112 #r113"/>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element substJoin
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.transcriptional.attributes,
   tei_att.dimensions.attributes,
   ( tei_model.descLike | tei_model.certLike )*
}

1.188. <summary>

<summary> contains an overview of the available information concerning some aspect of an item or object (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements. [11.6. Intellectual Content]
Modulemsdescription
Attributes
Contained by
May contain
Example
<summary>This item consists of three books with a prologue and an epilogue. </summary>
Example
<typeDesc>  <summary>Uses a mixture of Roman and Black Letter types.</summary>  <typeNote>Antiqua typeface, showing influence of Jenson's Venetian    fonts.</typeNote>  <typeNote>The black letter face is a variant of Schwabacher.</typeNote> </typeDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element summary { tei_att.global.attributes, tei_macro.specialPara }

1.189. <supplied>

<supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Attributes
reasonone or more words indicating why the text has had to be supplied, e.g. overbinding, faded-ink, lost-folio, omitted-in-original.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
Note

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

Example
I am dr Sr yr <supplied reason="illegible"  source="#amanuensis_copy">very humble Servt</supplied> Sydney Smith
Example
<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element supplied
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   attribute reason { list { + } }?,
   tei_macro.paraContent
}

1.190. <support>

<support> (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [11.7.1. Object Description]
Modulemsdescription
Attributes
Contained by
msdescription: supportDesc
May contain
Example
<objectDesc form="roll">  <supportDesc>   <support> Parchment roll with <material>silk</material> ribbons.   </support>  </supportDesc> </objectDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element support { tei_att.global.attributes, tei_macro.specialPara }

1.191. <supportDesc>

<supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [11.7.1. Object Description]
Modulemsdescription
Attributes
material(material) a short project-defined name for the material composing the majority of the support
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
paper
parch
(parchment)
mixed
Contained by
msdescription: objectDesc
May contain
core: p
header: extent
Example
<supportDesc>  <support> Parchment roll with <material>silk</material> ribbons.  </support> </supportDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="support" minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="foliation"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="collation"
    minOccurs="0"/>
   <elementRef key="condition"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element supportDesc
{
   tei_att.global.attributes,
   attribute material { "paper" | "parch" | "mixed" }?,
   (
      tei_model.pLike+
    | (
         tei_support?,
         tei_extent?,
         tei_foliation*,
         tei_collation?,
         tei_condition?
      )
   )
}

1.192. <surface>

<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and, when using an embedded transcription approach, transcriptions of the writing within them. [12.1. Digital Facsimiles 12.2.2. Embedded Transcription]
Moduletranscr
Attributes
attachmentdescribes the method by which this surface is or was connected to the main surface
StatusOptional
Datatypeteidata.enumerated
Sample values include:
glued
glued in place
pinned
pinned or stapled in place
sewn
sewn in place
flippingindicates whether the surface is attached and folded in such a way as to provide two writing surfaces
StatusOptional
Datatypeteidata.truthValue
Contained by
May contain
Note

The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.

The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.

The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid.

Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> element.

Example
<facsimile>  <surface ulx="0uly="0lrx="200lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.graphicLike"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="zone"/>
    <elementRef key="line"/>
    <elementRef key="path"/>
    <elementRef key="surface"/>
    <elementRef key="surfaceGrp"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element surface
{
   tei_att.global.attributes,
   tei_att.coordinated.attributes,
   tei_att.declaring.attributes,
   tei_att.typed.attributes,
   attribute attachment { text }?,
   attribute flipping { text }?,
   (
      ( tei_model.global | tei_model.labelLike | tei_model.graphicLike )*,
      (
         ( tei_zone | tei_line | tei_path | tei_surface | tei_surfaceGrp ),
         tei_model.global*
      )*
   )
}

1.193. <surfaceGrp>

<surfaceGrp> (surface group) defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [12.1. Digital Facsimiles]
Moduletranscr
Attributes
Contained by
May contain
Note

Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements.

Example
<sourceDoc>  <surfaceGrp>   <surface ulx="0uly="0lrx="200"    lry="300">    <graphic url="Bovelles-49r.png"/>   </surface>   <surface ulx="0uly="0lrx="200"    lry="300">    <graphic url="Bovelles-49v.png"/>   </surface>  </surfaceGrp> </sourceDoc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.global"/>
  <elementRef key="surface"/>
  <elementRef key="surfaceGrp"/>
 </alternate>
</content>
    
Schema Declaration
element surfaceGrp
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.typed.attributes,
   ( tei_model.global | tei_surface | tei_surfaceGrp )+
}

1.194. <surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<surname type="combine">St John Stevas</surname>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element surname
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.195. <surplus>

<surplus> (surplus) marks text present in the source which the editor believes to be superfluous or redundant. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Attributes
reasonone or more words indicating why this text is believed to be superfluous, e.g. repeated, interpolated etc.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
Example
I am dr Sr yrs <surplus reason="repeated">yrs</surplus> Sydney Smith
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element surplus
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   attribute reason { list { + } }?,
   tei_macro.paraContent
}

1.196. <surrogates>

<surrogates> (surrogates) contains information about any representations of the manuscript or other object being described which may exist in the holding institution or elsewhere. [11.9. Additional Information]
Modulemsdescription
Attributes
Contained by
msdescription: additional
May contain
Example
<surrogates>  <bibl>   <title type="gmd">diapositive</title>   <idno>AM 74 a, fol.</idno>   <date>May 1984</date>  </bibl>  <bibl>   <title type="gmd">b/w prints</title>   <idno>AM 75 a, fol.</idno>   <date>1972</date>  </bibl> </surrogates>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element surrogates { tei_att.global.attributes, tei_macro.specialPara }

1.197. <taxonomy>

<taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
May contain
msdescription: msDesc
Note

The <taxonomy> contains one or more taxonomies defining any classificatory codes used elsewhere in the text. There are various tags which Syriaca.org uses to mark elements for a variety of purposes. Syriaca.org’s preferred name forms are tagged with "syriaca-headword", for example.

Example
<classDecl>  <taxonomy>   <category xml:id="syriaca-headword">    <catDesc>The name used by Syriaca.org for document titles, citation, and        disambiguation. These names have been created according to the Syriac.org        guidelines for headwords: <ref target="http://syriaca.org/documentation/headwords.html">http://syriaca.org/documentation/headwords.html</ref>.</catDesc>   </category>  </taxonomy> </classDecl>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence minOccurs="1" maxOccurs="1">
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <classRef key="model.descLike"
      minOccurs="1" maxOccurs="1"/>
     <elementRef key="equiv" minOccurs="1"
      maxOccurs="1"/>
     <elementRef key="gloss" minOccurs="1"
      maxOccurs="1"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.biblLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element taxonomy
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   (
      (
         ( tei_category | tei_taxonomy )+
       | (
            ( tei_model.descLike | equiv | gloss )+,
            ( tei_category | tei_taxonomy )*
         )
      )
    | ( tei_model.biblLike, ( tei_category | tei_taxonomy )* )
   )
}

1.198. <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text]
Moduleheader
Attributes
Contained by
textstructure: TEI
May contain
Note

Every <teiHeader> element contains a <fileDesc> element (information about the creation of a file), an <encodingDesc> element (editorial rules), a <profileDesc> element (non-bibliographic aspects of a text), and a <revisionDesc> element (history of revisions).

Example
<teiHeader>  <fileDesc>   <titleStmt>    <title>Shakespeare: the first folio (1623) in electronic form</title>    <author>Shakespeare, William (1564–1616)</author>    <respStmt>     <resp>Originally prepared by</resp>     <name>Trevor Howard-Hill</name>    </respStmt>    <respStmt>     <resp>Revised and edited by</resp>     <name>Christine Avern-Carr</name>    </respStmt>   </titleStmt>   <publicationStmt>    <distributor>Oxford Text Archive</distributor>    <address>     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>    </address>    <idno type="OTA">119</idno>    <availability>     <p>Freely available on a non-commercial basis.</p>    </availability>    <date when="1968">1968</date>   </publicationStmt>   <sourceDesc>    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,        1968)</bibl>   </sourceDesc>  </fileDesc>  <encodingDesc>   <projectDesc>    <p>Originally prepared for use in the production of a series of old-spelling        concordances in 1968, this text was extensively checked and revised for use during the        editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>   </projectDesc>   <editorialDecl>    <correction>     <p>Turned letters are silently corrected.</p>    </correction>    <normalization>     <p>Original spelling and typography is retained, except that long s and ligatured          forms are not encoded.</p>    </normalization>   </editorialDecl>   <refsDecl xml:id="ASLREF">    <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"     replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">     <p>A reference is created by assembling the following, in the reverse order as that          listed here: <list>       <item>the <att>n</att> value of the preceding <gi>lb</gi>       </item>       <item>a period</item>       <item>the <att>n</att> value of the ancestor <gi>div2</gi>       </item>       <item>a space</item>       <item>the <att>n</att> value of the parent <gi>div1</gi>       </item>      </list>     </p>    </cRefPattern>   </refsDecl>  </encodingDesc>  <revisionDesc>   <list>    <item>     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>    <item>     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>   </list>  </revisionDesc> </teiHeader>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="fileDesc" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="encodingDesc"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="profileDesc"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="revisionDesc"
   minOccurs="1" maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   tei_att.global.attributes,
   ( tei_fileDesc, tei_encodingDesc, tei_profileDesc, tei_revisionDesc )
}

1.199. <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure
Member of
Contained by
textstructure: TEI
May contain
certainty: precision
core: note
linking: link
textcrit: app witDetail
textstructure: back body front
Note

The data of the record is contained within the <text> element. The Srophé App requires that all source attributes inside the <text> element point to an xml:id attribute on a <bibl> or <listBibl> element.

Example
<text    xmlns:srophe="https://srophe.app">  <body>   <listPlace>    <place type="diocese">     <placeName resp="http://syriaca.org"      xml:id="name3053-1xml:lang="en"      srophe:tags="#syriaca-headword">Arethusa</placeName>     <placeName resp="http://syriaca.org"      xml:id="name3053-2xml:lang="syr"      srophe:tags="#syriaca-headword">ܐܪܝܣܬܢ</placeName>     <placeName xml:id="name3053-3"      xml:lang="ensource="#bib3053-1">Arethusa</placeName>     <placeName xml:id="name3053-4"      xml:lang="syrsource="#bib3053-2">ܐܪܝܣܬܢ</placeName>     <desc type="abstract"      xml:id="abstract3053-1xml:lang="en">The diocese associated with the city of Arethusa</desc>     <state resp="http://syriaca.org"      type="existence"/>     <idno type="URI">http://syriaca.org/place/3053</idno>     <bibl xml:id="bib3053-1">      <ptr target="http://syriaca.org/bibl/668"/>      <citedRange unit="p">73</citedRange>     </bibl>     <bibl xml:id="bib3053-2">      <ptr target="http://syriaca.org/bibl/666"/>      <citedRange unit="p">81</citedRange>     </bibl>    </place>   </listPlace>  </body> </text>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element text
{
   tei_model.global*,
   ( tei_front, tei_model.global* )?,
   ( tei_body | group ),
   tei_model.global*,
   ( tei_back, tei_model.global* )?
}

1.200. <textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May containEmpty element
Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
    
Schema Declaration
element textClass
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( classCode | catRef | keywords )*
}

1.201. <title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore
Attributes
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.

calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of
Contained by
May contain
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Example
<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>
Example
<title type="full">  <title type="main">Synthèse</title>  <title type="sub">an international journal for    epistemology, methodology and history of    science</title> </title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element title
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   tei_macro.paraContent
}

1.202. <titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
Note

Each <titleStmt> element contains (in order) one or more <title> elements, optional <sponsor> elements, optional <funder> elements, optional <principal> elements, one or more <sourceDesc> elements, and optional <respStmt> elements.

Example
<titleStmt>  <title level="axml:lang="en">Van</title>  <sponsor>Syriaca.org: The Syriac Reference Portal</sponsor>  <funder>The National Endowment for the Humanities</funder>  <funder>The International Balzan Prize Foundation</funder>  <editor role="creator"   ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas A. Carlson</editor>  <respStmt>   <resp>Data merging, Pleiades and Wikipedia linking, and XML by</resp>   <name ref="http://syriaca.org/documentation/editors.xml#tcarlson">Thomas A.      Carlson</name>  </respStmt>  <respStmt>   <resp>Wilmshurst index information entry by</resp>   <name ref="http://syriaca.org/documentation/editors.xml#adavis">Anthony      Davis</name>  </respStmt> </titleStmt>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="sponsor" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="funder" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="principal" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="editor" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="respStmt" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element titleStmt
{
   tei_att.global.attributes,
   (
      tei_title+,
      tei_sponsor*,
      tei_funder*,
      tei_principal*,
      tei_editor+,
      tei_respStmt*
   )
}

1.203. <trait>

<trait> (trait) contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range. [14.3.1. Basic Principles 14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
certainty: precision
msdescription: msDesc
namesdates: trait
Note

Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<trait type="physical">  <label>Eye colour</label>  <desc>Blue</desc> </trait>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="trait" minOccurs="1"
    maxOccurs="unbounded"/>
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.headLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element trait
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      tei_precision*,
      (
         tei_trait+
       | (
            tei_model.headLike*,
            tei_model.pLike+,
            ( tei_model.noteLike | tei_model.biblLike )*
         )
       | ( tei_model.labelLike | tei_model.noteLike | tei_model.biblLike )*
      )
   )
}

1.204. <transpose>

<transpose> describes a single textual transposition as an ordered list of at least two pointers specifying the order in which the elements indicated should be re-combined. [12.3.4.5. Transpositions]
Moduletranscr
Attributes
Contained by
transcr: listTranspose
May contain
core: ptr
Note

Transposition is usually indicated in a document by a metamark such as a wavy line or numbering.

The order in which <ptr> elements appear within a <transpose> element should correspond with the desired order, as indicated by the metamark.

Example
<transpose>  <ptr target="#ib02"/>  <ptr target="#ib01"/> </transpose>
The transposition recorded here indicates that the content of the element with identifier ib02 should appear before the content of the element with identifier ib01.
Content model
<content>
 <elementRef key="ptr" minOccurs="2"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element transpose { tei_att.global.attributes, ( tei_ptr, tei_ptr, tei_ptr* ) }

1.205. <typeDesc>

<typeDesc> (typeface description) contains a description of the typefaces or other aspects of the printing of an incunable or other printed source. [11.7.2.1. Writing]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: summary typeNote
Example
<typeDesc>  <p>Uses an unidentified black letter font, probably from the    15th century</p> </typeDesc>
Example
<typeDesc>  <summary>Contains a mixture of blackletter and Roman (antiqua) typefaces</summary>  <typeNote xml:id="Frak1">Blackletter face, showing    similarities to those produced in Wuerzburg after 1470.</typeNote>  <typeNote xml:id="Rom1">Roman face of Venetian origins.</typeNote> </typeDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="typeNote" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element typeDesc
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_summary?, tei_typeNote+ ) )
}

1.206. <typeNote>

<typeNote> (typographic note) describes a particular font or other significant typographic feature distinguished within the description of a printed resource. [11.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
Attributes
Contained by
msdescription: typeDesc
May contain
Example
<typeNote scope="sole"> Printed in an Antiqua typeface showing strong Italianate influence. </typeNote>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element typeNote
{
   tei_att.global.attributes,
   tei_att.handFeatures.attributes,
   tei_macro.specialPara
}

1.207. <undo>

<undo> indicates one or more marked-up interventions in a document which have subsequently been marked for cancellation. [12.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
Moduletranscr
Attributes
targetpoints to one or more elements representing the interventions which are to be reverted or undone.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May containEmpty element
Example
<line>This is <del change="#s2rend="overstrike">   <seg xml:id="undo-a">just some</seg>    sample <seg xml:id="undo-b">text</seg>,    we need</del>  <add change="#s2">not</add> a real example.</line> <undo target="#undo-a #undo-b"  rend="dottedchange="#s3"/>
This encoding represents the following sequence of events:
  • "This is just some sample text, we need a real example" is written
  • At stage s2, "just some sample text, we need" is deleted by overstriking, and "not" is added
  • At stage s3, parts of the deletion are cancelled by underdotting, thus reinstating the words "just some" and "text".
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element undo
{
   tei_att.global.attributes,
   tei_att.spanning.attributes,
   tei_att.transcriptional.attributes,
   tei_att.dimensions.attributes,
   attribute target { list { + } }?,
   empty
}

1.208. <variantEncoding>

<variantEncoding> (variant encoding) declares the method used to encode text-critical variants. [13.1.1. The Apparatus Entry]
Moduletextcrit
Attributes
methodindicates which method is used to encode the apparatus of variants.
StatusRequired
Datatypeteidata.enumerated
Legal values are:
location-referenced
apparatus uses line numbers or other canonical reference scheme referenced in a base text.
double-end-point
apparatus indicates the precise locations of the beginning and ending of each lemma relative to a base text.
parallel-segmentation
alternate readings of a passage are given in parallel in the text; no notion of a base text is necessary.
Note

The value ‘parallel-segmentation’ requires in-line encoding of the apparatus.

locationindicates whether the apparatus appears within the running text or external to it.
StatusRequired
Datatypeteidata.enumerated
Schematron
<sch:rule context="tei:variantEncoding"> <sch:report test="@location eq 'external' and @method eq 'parallel-segmentation'"> The @location value "external" is inconsistent with the parallel-segmentation method of apparatus markup.</sch:report> </sch:rule>
Legal values are:
internal
apparatus appears within the running text.
external
apparatus appears outside the base text.
Note

The value ‘external’ is inconsistent with the parallel-segmentation method of apparatus markup.

Contained by
May containEmpty element
Example
<variantEncoding method="location-referenced"  location="external"/>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element variantEncoding
{
   tei_att.global.attributes,
   attribute method
   {
      "location-referenced" | "double-end-point" | "parallel-segmentation"
   },
   attribute location { "internal" | "external" },
   empty
}

1.209. <watermark>

<watermark> (watermark) contains a word or phrase describing a watermark or similar device. [11.3.3. Watermarks and Stamps]
Modulemsdescription
Attributes
Member of
Contained by
May contain
Example
<support>  <p>   <material>Rag paper</material> with <watermark>anchor</watermark> watermark</p> </support>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element watermark { tei_att.global.attributes, tei_macro.phraseSeq }

1.210. <width>

<width> (width) contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [11.3.4. Dimensions]
Modulemsdescription
Attributes
Member of
Contained by
May containCharacter data only
Note

If used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis.

Example
<width unit="in">4</width>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element width
{
   tei_att.global.attributes,
   tei_att.dimensions.attributes,
   tei_macro.xtext
}

1.211. <wit>

<wit> (wit) contains a list of one or more sigla of witnesses attesting a given reading, in a textual variation. [13.1.4. Witness Information]
Moduletextcrit
Attributes
Member of
Contained by
textcrit: app lem rdg rdgGrp
May contain
Note

This element represents the same information as that provided by the wit attribute of the reading; it may be used to record the exact form of the sigla given in the source edition, when that is of interest.

Example
<rdg wit="#El #Hg">Experience</rdg> <wit>Ellesmere, Hengwryt</wit>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element wit
{
   tei_att.global.attributes,
   tei_att.rdgPart.attributes,
   tei_macro.phraseSeq
}

1.212. <witDetail>

<witDetail> (witness detail) gives further information about a particular witness, or witnesses, to a particular reading. [13.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit
Attributes
typedescribes the type of information given about the witness.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
wit(witnesses) indicates the sigil or sigla identifying the witness or witnesses to which the detail refers.
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May contain
Note

The <witDetail> element was formerly permitted anywhere that <note> could appear, but since it should only be used in association with <lem> and <rdg>, it is recommended that it be placed immediately following the reading that it modifies, in the same <app>. A <witDetail> without a target attribute should be assumed to refer to the closest preceding <lem> or <rdg>.

Example
<app type="substantive">  <lem xml:id="W026xwit="#El #HG">Experience</lem>  <rdg wit="#Ha4">Experiens</rdg>  <witDetail target="#W026xresp="#PR"   wit="#Eltype="presentation">Ornamental capital.</witDetail> </app>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
  <elementRef key="bibl"/>
 </alternate>
</content>
    
Schema Declaration
element witDetail
{
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute wit { list { + } },
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global | tei_bibl )*
}

1.213. <witEnd>

<witEnd> (fragmented witness end) indicates the end, or suspension, of the text of a fragmentary witness. [13.1.5. Fragmentary Witnesses]
Moduletextcrit
Attributes
Member of
Contained by
textcrit: lem rdg
May containEmpty element
Example
<app>  <lem wit="#El #Hg">Experience</lem>  <rdg wit="#Ha4">Ex<g ref="#per"/>   <witEnd/>  </rdg> </app>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element witEnd { tei_att.global.attributes, tei_att.rdgPart.attributes, empty }

1.214. <witStart>

<witStart> (fragmented witness start) indicates the beginning, or resumption, of the text of a fragmentary witness. [13.1.5. Fragmentary Witnesses]
Moduletextcrit
Attributes
Member of
Contained by
textcrit: lem rdg
May containEmpty element
Example
<app>  <lem wit="#El #Hg">Auctoritee</lem>  <rdg wit="#La #Ra2">auctorite</rdg>  <rdg wit="#X">   <witStart/>auctorite</rdg> </app>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element witStart
{
   tei_att.global.attributes,
   tei_att.rdgPart.attributes,
   empty
}

1.215. <witness>

<witness> (witness) contains either a description of a single witness referred to within the critical apparatus, or a list of witnesses which is to be referred to by a single sigil. [13.1. The Apparatus Entry, Readings, and Witnesses]
Moduletextcrit
Attributes
Contained by
textcrit: listWit
May contain
Note

The content of the <witness> element may give bibliographic information about the witness or witness group, or it may be empty.

Example
<listWit>  <witness xml:id="EL">Ellesmere, Huntingdon Library 26.C.9</witness>  <witness xml:id="HG">Hengwrt, National Library of Wales,    Aberystwyth, Peniarth 392D</witness>  <witness xml:id="RA2">Bodleian Library Rawlinson Poetic 149    (see further <ptr target="http://www.examples.com/MSdescs#MSRP149"/>)</witness> </listWit>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
  <elementRef key="note"/>
  <elementRef key="object"/>
 </alternate>
</content>
    
Schema Declaration
element witness
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   ( text | tei_model.limitedPhrase | tei_model.inter | tei_note | object )*
}

1.216. <zone>

<zone> defines any two-dimensional area within a <surface> element. [12.1. Digital Facsimiles 12.2.2. Embedded Transcription]
Moduletranscr
Attributes
rotateindicates the amount by which this zone has been rotated clockwise, with respect to the normal orientation of the parent <surface> element as implied by the dimensions given in the <msDesc> element or by the coordinates of the <surface> itself. The orientation is expressed in arc degrees.
StatusOptional
Datatypeteidata.count
Default0
Member of
Contained by
transcr: line surface zone
May contain
Note

The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface.

A graphic element contained by a zone represents the whole of the zone.

A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.

A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the <path> element.

Example
<surface ulx="14.54uly="16.14lrx="0"  lry="0">  <graphic url="stone.jpg"/>  <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/> </surface>
This example defines a non-rectangular zone: see the illustration in section [[undefined PH-surfzone]].
Example
<facsimile>  <surface ulx="50uly="20lrx="400"   lry="280">   <zone ulx="0uly="0lrx="500lry="321">    <graphic url="graphic.png"/>   </zone>  </surface> </facsimile>
This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <elementRef key="surface"/>
  <classRef key="model.linePart"/>
 </alternate>
</content>
    
Schema Declaration
element zone
{
   tei_att.global.attributes,
   tei_att.coordinated.attributes,
   tei_att.typed.attributes,
   tei_att.written.attributes,
   attribute rotate { text }?,
   (
      text
    | tei_model.gLike
    | tei_model.graphicLike
    | tei_model.global
    | tei_surface
    | tei_model.linePart
   )*
}

2. Model classes

2.1. model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source.
Moduletei
Used by
Membersmodel.quoteLike[quote]

2.2. model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement
Moduletei
Used by
Memberslicence

2.3. model.biblLike

model.biblLike groups elements containing a bibliographic description.
Moduletei
Used by
Membersbibl listBibl msDesc

2.4. model.biblPart

model.biblPart groups elements which represent components of a bibliographic description.
Moduletei
Used by
Membersmodel.imprintPart[biblScope pubPlace] model.respLike[author editor funder principal respStmt sponsor] availability bibl citedRange decoNote edition explicit extent incipit listRelation msIdentifier quote

2.5. model.certLike

model.certLike groups elements which are used to indicate uncertainty or precision of other elements.
Moduletei
Used by
Membersprecision

2.6. model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation.
Moduletei
Used by
Membersabbr am corr ex expan orig reg sic supplied

2.7. model.common

model.common groups common chunk- and inter-level elements.
Moduletei
Used by
Membersmodel.cmc model.divPart[model.lLike model.pLike[p]] model.entryLike[entryFree] model.inter[model.attributable[model.quoteLike[quote]] model.biblLike[bibl listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listApp listPerson listPlace listRelation listWit] model.oddDecl model.stageLike]
Note

This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

2.8. model.dateLike

model.dateLike groups elements containing temporal expressions.
Moduletei
Used by
Membersdate

2.9. model.descLike

model.descLike groups elements which contain a description of their function.
Moduletei
Used by
Membersdesc

2.10. model.dimLike

model.dimLike groups elements which describe a measurement forming part of the physical dimensions of some object.
Moduletei
Used by
Membersdepth height width

2.11. model.divBottom

model.divBottom groups elements appearing at the end of a text division.
Moduletei
Used by
Membersmodel.divBottomPart model.divWrapper

2.12. model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Moduletei
Used by
Membersdiv

2.13. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions.
Moduletei
Used by
Membersmodel.lLike model.pLike[p]
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

2.14. model.divTop

model.divTop groups elements appearing at the beginning of a text division.
Moduletei
Used by
Membersmodel.divTopPart[model.headLike[head]] model.divWrapper

2.15. model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division.
Moduletei
Used by
Membersmodel.headLike[head]

2.16. model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed.
Moduletei
Used by
Membersforeign title

2.17. model.entryLike

model.entryLike groups elements structurally analogous to paragraphs within dictionaries.
Moduledictionaries
Used by
MembersentryFree

2.18. model.eventLike

model.eventLike groups elements which describe events.
Moduletei
Used by
Membersevent

2.19. model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter.
Moduletei
Used by
Membersmodel.frontPart.drama listBibl

2.21. model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function.
Moduletei
Used by
MembersaddSpan app damageSpan delSpan space witDetail

2.22. model.global.meta

model.global.meta groups globally available elements which describe the status of other elements.
Moduletei
Used by
Memberslink listTranspose precision substJoin
Note

Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

2.23. model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects.
Moduletei
Used by
Membersformula

2.24. model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei
Used by
Membershead

2.25. model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct.
Moduletei
Used by
Membersmodel.emphLike[foreign title] model.hiLike

2.26. model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints.
Moduletei
Used by
MembersbiblScope pubPlace

2.27. model.inter

model.inter groups elements which can appear either within or between paragraph-like elements.
Moduletei
Used by
Membersmodel.attributable[model.quoteLike[quote]] model.biblLike[bibl listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listApp listPerson listPlace listRelation listWit] model.oddDecl model.stageLike

2.28. model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei
Used by
Membersdesc label

2.30. model.linePart

model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Moduletei
Used by
Membersmodel.hiLike choice damage handShift line mod path redo restore retrace undo zone

2.31. model.listLike

model.listLike groups list-like elements.
Moduletei
Used by
Memberslist listApp listPerson listPlace listRelation listWit

2.32. model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning.
Moduletei
Used by
Membersdepth dim geo height measure width

2.33. model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems.
Moduletei
Used by
Membersfw

2.34. model.msItemPart

2.35. model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Moduletei
Used by
Memberscolophon explicit finalRubric incipit rubric title

2.36. model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike[offset] model.persNamePart[addName forename roleName surname] model.placeStateLike[model.placeNamePart[bloc country district placeName region settlement] location state trait] idno rs
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

2.37. model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies.
Moduletei
Used by
Membersname orgName persName
Note

This class is used in the content model of elements which reference names of people or organizations.

2.38. model.noteLike

model.noteLike groups globally-available note-like elements.
Moduletei
Used by
Membersnote

2.39. model.offsetLike

model.offsetLike groups elements which can appear only as part of a place name.
Moduletei
Used by
Membersoffset

2.41. model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter.
Moduletei
Used by
Membershead

2.43. model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription.
Moduletei
Used by
Membersmodel.pPart.editorial[abbr am choice ex expan subst] model.pPart.transcriptional[corr damage handShift mod orig redo reg restore retrace secl sic supplied surplus undo]

2.44. model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring.
Moduletei
Used by
Membersabbr am choice ex expan subst

2.45. model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description.
Moduletei
Used by
Memberscatchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark

2.46. model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials.
Moduletei
Used by
Memberscorr damage handShift mod orig redo reg restore retrace secl sic supplied surplus undo

2.47. model.paraPart

2.48. model.persNamePart

model.persNamePart groups elements which form part of a personal name.
Modulenamesdates
Used by
MembersaddName forename roleName surname

2.49. model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Moduletei
Used by
Membersfloruit gender occupation persName state trait
Note

These characteristics of an individual are typically a consequence of their own action or that of others.

2.50. model.personLike

model.personLike groups elements which provide information about people and their relationships.
Moduletei
Used by
Membersperson personGrp

2.51. model.personPart

model.personPart groups elements which form part of the description of a person.
Moduletei
Used by
Membersmodel.biblLike[bibl listBibl msDesc] model.eventLike[event] model.persStateLike[floruit gender occupation persName state trait] birth death idno name

2.53. model.phrase.xml

model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values
Moduletei
Used by
Membersgi

2.54. model.physDescPart

model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source.
Modulemsdescription
Used by
MembersaccMat additions bindingDesc decoDesc handDesc musicNotation objectDesc scriptDesc sealDesc typeDesc

2.55. model.placeLike

model.placeLike groups elements used to provide information about places and their relationships.
Moduletei
Used by
Membersplace

2.56. model.placeNamePart

model.placeNamePart groups elements which form part of a place name.
Moduletei
Used by
Membersbloc country district placeName region settlement

2.57. model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
Membersmodel.placeNamePart[bloc country district placeName region settlement] location state trait

2.58. model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Moduletei
Used by
MembershandNotes langUsage listTranspose textClass

2.59. model.ptrLike

model.ptrLike groups elements used for purposes of location and reference.
Moduletei
Used by
Membersptr ref

2.60. model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei
Used by
Membersquote

2.61. model.rdgLike

model.rdgLike groups elements which contain a single reading, other than the lemma, within a textual variation.
Moduletextcrit
Used by
Membersrdg
Note

This class allows for variants of the <rdg> element to be easily created via TEI customizations.

2.62. model.rdgPart

model.rdgPart groups elements which mark the beginning or ending of a fragmentary manuscript or other witness.
Moduletextcrit
Used by
MemberslacunaEnd lacunaStart wit witEnd witStart
Note

These elements may appear anywhere within the elements <lem> and <rdg>, and also within any of their constituent elements.

2.63. model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata.
Moduletei
Used by
Membersfacsimile sourceDoc text

2.64. model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei
Used by
Membersauthor editor funder principal respStmt sponsor

3. Attribute classes

3.1. att.anchoring

att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
Moduletei
Membersnote
Attributes
anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Note

In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

targetEnd(target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 17.2.4.6. range().

Example
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <noteGrp targetEnd="#A55234">  <note xml:lang="en"> Quatuor Tempora, so called dry fast days.  </note>  <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.  </note> </noteGrp>

3.2. att.cReferencing

att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
Moduletei
Membersptr ref
Attributes
cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
StatusOptional
Datatypeteidata.text
Note

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 17.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

3.3. att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs.
Moduletei
Membersdate origDate
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"  when="1732-02-22">Feb. 11, 1731/32, O.S.</date>).
He was born on <date calendar="#gregorian #julian"  when="1732-02-22">Feb. 22, 1732 (Feb. 11, 1731/32, O.S.)</date>.
Note

Note that the calendar attribute declares the calendar system used to interpret the textual content of an element, as it appears on an original source. It does not modify the interpretation of the normalization attributes provided by att.datable.w3c, att.datable.iso, or att.datable.custom. Attributes from those first two classes are always interpreted as Gregorian or proleptic Gregorian dates, as per the respective standards on which they are based. The calender system used to interpret the last (att.datable.custom) may be specified with datingMethod.

3.4. att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
Moduletei
Membersatt.naming[att.personal[addName forename name orgName persName placeName roleName surname] author birth bloc collection country death district editor event institution occupation offset origPlace pubPlace region repository rs settlement state trait] authority catDesc date funder material objectType principal relation resp respStmt sponsor title
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
StatusOptional
Datatypeteidata.text
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent. No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project.

ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"  type="person">Seamus Heaney</name>
Note

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

ExampleIn this contrived example, a canonical reference to the same organisation is provided in four different ways.
<author n="1">  <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="2">  <name ref="nzvn:427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="3">  <name ref="./named_entities.xml#o427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="4">  <name key="name-427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>
The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange.

These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange.

3.5. att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited.
Moduletei
MembersbiblScope citedRange
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(chapter) the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
fromspecifies the starting point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word
tospecifies the end-point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word

3.6. att.cmc

att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.
Moduletei
Membersabbr addName bibl bloc choice corr country date desc district expan foreign forename formula geo head idno label link list listBibl listPerson listPlace listRelation location measure name note offset orgName orig p persName placeName ptr quote ref reg region roleName rs settlement sic state surname title trait
Attributes
generatedBy(generated by) categorizes how the content of an element was generated in a CMC environment.
StatusOptional
Datatypeteidata.enumerated
Schematron
<sch:rule context="tei:*[@generatedBy]"> <sch:assert test="ancestor-or-self::tei:post">The @generatedBy attribute is for use within a <post> element.</sch:assert> </sch:rule>
Suggested values include:
human
the content was ‘naturally’ typed or spoken by a human user
template
the content was generated after a human user activated a template for its insertion
system
the content was generated by the system, i.e. the CMC environment
bot
the content was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself
unspecified
the content was generated by an unknown or unspecified process
automatic system message in chat: user moves on to another chatroom
<post type="event"  generatedBy="system"  who="#system"  rend="color:blue">  <p>   <name type="nickname"    corresp="#A02">McMike</name> geht    in einen anderen Raum: <name type="roomname">Kreuzfahrt</name>  </p> </post>
automatic system message in chat: user enters a chatroom
<post type="event"  generatedBy="system">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> betritt    den Raum. </p> </post>
automatic system message in chat: user changes his font color
<post type="event"  generatedBy="system"  rend="color:red">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> hat die    Farbe gewechselt.  </p> </post>
An automatic signature of user including an automatic timestamp (Wikipedia discussion, anonymized). The specification of generatedBy at the inner element <signed> is meant to override the specification at the outer element <post>. This is generally possible when the outer generatedBy value is "human".
<post type="standard"  generatedBy="human"  indentLevel="2"  synch="#t00394407"  who="#WU00005582">  <p> Kurze Nachfrage: Die Hieros für den Goldnamen stammen    auch von Beckerath gem. Literatur ? Grüße --</p>  <signed generatedBy="template"   rend="inline">   <gap reason="signatureContent"/>   <time generatedBy="template">18:50, 22. Okt. 2008 (CEST)</time>  </signed> </post>
Wikipedia talk page: user signature
<post type="written"  generatedBy="human">  <signed generatedBy="template">   <gap reason="signatureContent"/>   <time generatedBy="template">12:01, 12. Jun. 2009 (CEST)</time>  </signed> </post>

3.7. att.coordinated

att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
Moduletranscr
Membersline path surface zone
Attributes
startindicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
StatusOptional
Datatypeteidata.pointer
ulxgives the x coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
ulygives the y coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
lrxgives the x coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
lrygives the y coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
pointsidentifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
StatusOptional
Datatype3–∞ occurrences of teidata.point separated by whitespace

3.8. att.damaged

att.damaged provides attributes describing the nature of any physical damage affecting a reading.
Moduletei
Membersdamage damageSpan
Attributes
agentcategorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
degreeprovides a coded representation of the degree of damage, either as a number between 0 (undamaged) and 1 (very extensively damaged), or as one of the codes high, medium, low, or unknown. The <damage> element with the degree attribute should only be used where the text may be read with some confidence; text supplied from other sources should be tagged as <supplied>.
StatusOptional
Datatypeteidata.probCert
Note

The <damage> element is appropriate where it is desired to record the fact of damage although this has not affected the readability of the text, for example a weathered inscription. Where the damage has rendered the text more or less illegible either the <unclear> tag (for partial illegibility) or the <gap> tag (for complete illegibility, with no text supplied) should be used, with the information concerning the damage given in the attribute values of these tags. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of the use of these tags in particular circumstances.

groupassigns an arbitrary number to each stretch of damage regarded as forming part of the same physical phenomenon.
StatusOptional
Datatypeteidata.count

3.9. att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events.
Moduletei
Membersacquisition altIdentifier author binding birth bloc change country custEvent date death district editor event floruit funder gender idno licence location name occupation offset orgName origDate origPlace origin persName placeName precision principal provenance region relation resp seal settlement sponsor stamp state title trait
Attributes
srophe:computed-startStart date for a Srophe timeline
StatusOptional
Datatype1–∞ occurrences of teidata.temporal.w3c separated by whitespace
srophe:computed-endEnd date for a Srophe timeline
StatusOptional
Datatype1–∞ occurrences of teidata.temporal.w3c separated by whitespace
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s or <event>s) within which the datable item is understood to have occurred.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

3.10. att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO).
Modulenamesdates
Membersatt.datable[acquisition altIdentifier author binding birth bloc change country custEvent date death district editor event floruit funder gender idno licence location name occupation offset orgName origDate origPlace origin persName placeName precision principal provenance region relation resp seal settlement sponsor stamp state title trait]
Attributes
when-customsupplies the value of a date or time in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the <date when="1040-03-06"   when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH  </date>.</p> <p>The current world will end at the <date when="2012-12-21"   when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p> <p>The Battle of Meggidu (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p> <p>Esidorus bixit in pace annos LXX plus minus sub <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date> </p>
Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-customspecifies the earliest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
notAfter-customspecifies the latest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
from-customindicates the starting point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<event xml:id="FIRE1"  datingMethod="#julian"  from-custom="1666-09-02"  to-custom="1666-09-05">  <head>The Great Fire of London</head>  <p>The Great Fire of London burned through a large part    of the city of London.</p> </event>
to-customindicates the ending point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
StatusOptional
Datatypeteidata.pointer
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
StatusOptional
Datatypeteidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne eſtate, and deſcription of that Citie, written in the yeare <date when-custom="1598"  calendar="#julian"  datingMethod="#julian">1598</date>. by Iohn Stow Citizen of London.
In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
<date when="1382-06-28"  when-custom="6890-06-20"  datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num> </date>
In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

3.11. att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard.
Modulenamesdates
Membersatt.datable[acquisition altIdentifier author binding birth bloc change country custEvent date death district editor event floruit funder gender idno licence location name occupation offset orgName origDate origPlace origin persName placeName precision principal provenance region relation resp seal settlement sponsor stamp state title trait]
Attributes
when-isosupplies the value of a date or time in a standard form.
StatusOptional
Datatypeteidata.temporal.iso
The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date> <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date> <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time> <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time> <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date> <time when-iso="03:00">3 A.M.</time> <time when-iso="14">around two</time> <time when-iso="15,5">half past three</time>
All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q>  <time when-iso="12">around noon</time> </q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
from-isoindicates the starting point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
to-isoindicates the ending point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601:2004, using the Gregorian calendar.

If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date when-iso="2007-06-01dur-iso="P8D"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

3.12. att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
Moduletei
Membersatt.datable[acquisition altIdentifier author binding birth bloc change country custEvent date death district editor event floruit funder gender idno licence location name occupation offset orgName origDate origPlace origin persName placeName precision principal provenance region relation resp seal settlement sponsor stamp state title trait]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Schematron
<sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to"  role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@from]"> <sch:report test="@notBefore"  role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report test="@notAfter"  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

3.13. att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them.
Moduletei
Membersatt.lexicographic[entryFree] category taxonomy
Attributes
datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
ExampleThe example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.
<fs>  <f name="POS"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">   <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"    value="NN"/>  </f> </fs>
‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]].
<fs>  <f name="POSfVal="#commonNoun"/> </fs>
The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">  <symbol xml:id="commonNounvalue="NN"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <symbol xml:id="properNounvalue="NP"   datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> </fvLib>
Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
ExampleIn the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.
<gramGrp>  <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true">  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="pos"    targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>   <tagUsage gi="case"    targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage>  </namespace> </tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>  <prefixDef ident="ccrmatchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccrmatchPattern="adj"   replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <entry>  <form>   <orth>isotope</orth>  </form>  <gramGrp>   <pos datcat="ccr:pos"    valueDatcat="ccr:adj">adj</pos>  </gramGrp> </entry>
This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>.
ExampleThe <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc>  <classDecl>   <taxonomy xml:id="UD-SYN"    datcat="https://universaldependencies.org/u/dep/index.html">    <desc>     <term>UD syntactic relations</term>    </desc>    <category xml:id="acl"     valueDatcat="https://universaldependencies.org/u/dep/acl.html">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category xml:id="acl_relcl"     valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category xml:id="advcl"     valueDatcat="https://universaldependencies.org/u/dep/advcl.html">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category>   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
ExampleThe targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.
<fDecl name="POS"  targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">  <fDescr>part of speech (morphosyntactic category)</fDescr>  <vRange>   <vAlt>    <symbol value="NN"     datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>    <symbol value="NP"     datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>   </vAlt>  </vRange> </fDecl>
Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
ExampleThe att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<encodingDesc>  <classDecl>   <taxonomy xml:id="domains">    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category xml:id="domain.medical_and_health_sciences.medicine"      valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss/>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss/>      </catDesc>     </category>    </category>   </taxonomy>  </classDecl> </encodingDesc> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
Note

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container.

A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair <part-of-speech,common-noun>, namely <pos>commonNoun</pos> and pos="common-noun", one would classify the element <pos> and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

3.14. att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute.
Moduletei
Membersavailability bibl editorialDecl interpretation langUsage listApp listBibl listPerson listPlace seriesStmt sourceDesc textClass
Attributes
defaultindicates whether or not this element is selected by default when its parent is selected.
StatusOptional
Datatypeteidata.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

3.15. att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element.
Moduletei
Membersback body div facsimile front geo msDesc p ptr ref sourceDoc surface surfaceGrp
Attributes
decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text.

3.16. att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersatt.damaged[damage damageSpan] addSpan birth date death delSpan depth dim dimensions ex floruit height mod offset origDate redo restore retrace secl space state subst substJoin supplied surplus trait undo width
Attributes
unitnames the unit used for the measurement
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
StatusOptional
Datatypeteidata.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
StatusOptional
Datatypeteidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
StatusOptional
Datatypeteidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

3.17. att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions.
Moduletei
Membersdiv
Attributes
org(organization) specifies how the content of the division is organized.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
composite
no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
uniform
the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence.[Default]
sampleindicates whether this division is a sample of the original source and if so, from which part.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
initial
division lacks material present at end in source.
medial
division lacks material at start and end.
final
division lacks material at start.
unknown
position of sampled material within original unknown.
complete
division is not a sample.[Default]

3.18. att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei
Membersbibl change msDesc revisionDesc
Attributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change when="2010-10-21"   status="published"/>  <change when="2010-10-02status="cleared"/>  <change when="2010-08-02"   status="embargoed"/>  <change when="2010-05-01status="frozen"   who="#MSM"/>  <change when="2010-03-01status="draft"   who="#LB"/> </revisionDesc>

3.19. att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind.
Moduletei
Membersatt.transcriptional[addSpan delSpan mod redo restore retrace subst substJoin undo] am birth corr date death event ex expan floruit gender location name occupation offset orgName origDate origPlace origin persName person place placeName reg relation secl state supplied surplus trait
Attributes
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
StatusOptional
Datatypeteidata.xTruthValue
Defaultfalse
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

3.20. att.entryLike

att.entryLike provides attributes used to distinguish different styles of dictionary entries.
Moduledictionaries
MembersentryFree
Attributes
typeindicates type of entry, in dictionaries with multiple types.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
main
a main entry (default).[Default]
hom
(homograph) groups information relating to one homograph within an entry.
xref
(cross reference) a reduced entry whose only function is to point to another main entry (e.g. for forms of an irregular verb or for variant spellings: was pointing to be, or esthete to aesthete).
affix
an entry for a prefix, infix, or suffix.
abbr
(abbreviation) an entry for an abbreviation.
supplemental
a supplemental entry (for use in dictionaries which issue supplements to their main work in which they include updated information about entries).
foreign
an entry for a foreign word in a monolingual dictionary.
Note

The global n attribute may be used to encode the homograph numbers attached to entries for homographs.

3.21. att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Moduletei
Membersatt.divLike[div] p
Attributes
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be reconstituted.

3.22. att.global

att.global provides attributes common to all elements in the TEI encoding scheme.
Moduletei
MembersTEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptional
Datatypeteidata.text
Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
Note

The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at https://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptional
Datatypeteidata.pointer
<div type="bibl">  <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>  </head>  <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">   <bibl>    <ref target="letterEEd.26.3.xml">     <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.57.xml">     <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.85.xml">     <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05"      to="1794-04-06">5-6 April, 1794</date>.    </ref>   </bibl>  </listBibl> </div>
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

3.23. att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text.
Moduleanalysis
Membersatt.global[TEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone]
Attributes
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

3.24. att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Moduletranscr
Membersatt.global[TEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone]
Attributes
changepoints to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.25. att.global.facs

att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface.
Moduletranscr
Membersatt.global[TEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone]
Attributes
facs(facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.26. att.global.linking

att.global.linking provides a set of attributes for hypertextual linking.
Modulelinking
Membersatt.global[TEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone]
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<group>  <text xml:id="t1-g1-t1"   xml:lang="mi">   <body xml:id="t1-g1-t1-body1">    <div type="chapter">     <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>     <p></p>    </div>   </body>  </text>  <text xml:id="t1-g1-t2"   xml:lang="en">   <body xml:id="t1-g1-t2-body1"    corresp="#t1-g1-t1-body1">    <div type="chapter">     <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>     <p></p>    </div>   </body>  </text> </group>
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
<place xml:id="LOND1"  corresp="people.xml#LOND2 people.xml#GENI1">  <placeName>London</placeName>  <desc>The city of London...</desc> </place> <person xml:id="LOND2"  corresp="places.xml#LOND1 #GENI1">  <persName type="lit">London</persName>  <note>   <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>  </note> </person> <person xml:id="GENI1"  corresp="places.xml#LOND1 #LOND2">  <persName type="lit">London’s Genius</persName>  <note>   <p>Personification of London’s genius. Appears as an      allegorical character in mayoral shows.   </p>  </note> </person>
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
synch(synchronous) points to elements that are synchronous with the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
sameAspoints to an element that is the same as the current element.
StatusOptional
Datatypeteidata.pointer
copyOfpoints to an element of which the current element is a copy.
StatusOptional
Datatypeteidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

nextpoints to the next element of a virtual aggregate of which the current element is part.
StatusOptional
Datatypeteidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
StatusOptional
Datatypeteidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

excludepoints to elements that are in exclusive alternation with the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

3.27. att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme.
Moduletei
Membersatt.global[TEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rend="case(mixed)">New Blazing-World</hi>. </head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
StatusOptional
Datatypeteidata.text
<head style="text-align: center; font-variant: small-caps">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi style="font-variant: normal">New Blazing-World</hi>. </head>
Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

renditionpoints to a description of the rendering or presentation used for this element in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rendition="#normal">New Blazing-World</hi>. </head> <rendition xml:id="sc"  scheme="css">font-variant: small-caps</rendition> <rendition xml:id="normal"  scheme="css">font-variant: normal</rendition> <rendition xml:id="ac"  scheme="css">text-align: center</rendition>
Note

The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

3.28. att.global.responsibility

att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it.
Moduletei
Membersatt.global[TEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatypeteidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

Example
Blessed are the <choice>  <sic>cheesemakers</sic>  <corr resp="#editorcert="high">peacemakers</corr> </choice>: for they shall be called the children of God.
Example
<lg>  <l>Punkes, Panders, baſe extortionizing    sla<choice>    <sic>n</sic>    <corr resp="#JENS1_transcriber">u</corr>   </choice>es,</l> </lg> <respStmt xml:id="JENS1_transcriber">  <resp when="2014">Transcriber</resp>  <name>Janelle Jenstad</name> </respStmt>

3.29. att.global.source

att.global.source provides attributes used by elements to point to an external source.
Moduletei
Membersatt.global[TEI abbr accMat acquisition addName addSpan additional additions adminInfo altIdentifier am app author authority availability back bibl biblScope binding bindingDesc birth bloc body catDesc catchwords category change choice citedRange classDecl collation collection colophon condition corr country custEvent custodialHist damage damageSpan date death decoDesc decoNote delSpan depth desc dim dimensions district div edition editionStmt editor editorialDecl encodingDesc entryFree event ex expan explicit extent facsimile fileDesc filiation finalRubric floruit foliation foreign forename formula front funder fw gender geo gi handDesc handNote handNotes handShift head height heraldry history idno incipit institution interpretation item label lacunaEnd lacunaStart langUsage language layout layoutDesc lem licence line list listApp listBibl listPerson listPlace listRelation listTranspose listWit location locus locusGrp material measure metamark mod msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note objectDesc objectType occupation offset orgName orig origDate origPlace origin p path persName person personGrp physDesc place placeName precision principal profileDesc provenance ptr pubPlace publicationStmt quote rdg rdgGrp recordHist redo ref reg region relation repository resp respStmt restore retrace revisionDesc roleName rs rubric scriptDesc seal sealDesc secFol secl seriesStmt settlement sic signatures source sourceDesc sourceDoc space sponsor stamp state subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates taxonomy teiHeader textClass title titleStmt trait transpose typeDesc typeNote undo variantEncoding watermark width wit witDetail witEnd witStart witness zone]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Note

The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested    term.</quote> </p>
Example
<p>  <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the    less we seem to know.</quote> </p> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of    Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
Example
<elementRef key="psource="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"  source="mycompiledODD.xml"/>
Create a schema using components taken from the file mycompiledODD.xml.

3.30. att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written.
Moduletei
MembershandNote handShift typeNote
Attributes
scribegives a name or other identifier for the scribe believed to be responsible for this hand.
StatusOptional
Datatypeteidata.name
scribeRefpoints to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
StatusOptional
Datatype1–∞ occurrences of teidata.name separated by whitespace
scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a <scriptNote> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
scopespecifies how widely this hand is used in the manuscript.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
sole
only this hand is used throughout the manuscript
major
this hand is used through most of the manuscript
minor
this hand is used occasionally in the manuscript
Note

Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

3.31. att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
ExampleIn this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8"  target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

3.32. att.lexicographic

att.lexicographic provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts.
Moduledictionaries
MembersentryFree
Attributes
expand(expand) gives an expanded form of information presented more concisely in the dictionary
StatusOptional
Datatypeteidata.text
<gramGrp>  <pos expand="noun">n</pos> </gramGrp>
split(split) gives the list of split values for a merged form
StatusOptional
Datatypeteidata.text
value(value) gives a value which lacks any realization in the printed source text.
StatusOptional
Datatypeteidata.text
location(location) indicates an <anchor> element typically elsewhere in the document, but possibly in another document, which is the original location of this component.
StatusOptional
Datatypeteidata.pointer
mergedIn(merged into) gives a reference to another element, where the original appears as a merged form.
StatusOptional
Datatypeteidata.pointer
opt(optional) indicates whether the element is optional or not
StatusOptional
Datatypeteidata.truthValue
Defaultfalse

3.33. att.locatable

att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places.
Moduletei
Membersevent
Attributes
whereindicates one or more locations by pointing to a <place> element or other canonical description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.34. att.measurement

att.measurement provides attributes to represent a regularized or normalized measurement.
Moduletei
Membersmeasure
Attributes
unit(unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
m
(metre) SI base unit of length
kg
(kilogram) SI base unit of mass
s
(second) SI base unit of time
Hz
(hertz) SI unit of frequency
Pa
(pascal) SI unit of pressure or stress
Ω
(ohm) SI unit of electric resistance
L
(litre) 1 dm³
t
(tonne) 10³ kg
ha
(hectare) 1 hm²
Å
(ångström) 10⁻¹⁰ m
mL
(millilitre)
cm
(centimetre)
dB
(decibel) see remarks, below
kbit
(kilobit) 10³ or 1000 bits
Kibit
(kibibit) 2¹⁰ or 1024 bits
kB
(kilobyte) 10³ or 1000 bytes
KiB
(kibibyte) 2¹⁰ or 1024 bytes
MB
(megabyte) 10⁶ or 1 000 000 bytes
MiB
(mebibyte) 2²⁰ or 1 048 576 bytes
Note

If the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.

Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.

unitRefpoints to a unique identifier stored in the xml:id of a <unitDef> element that defines a unit of measure.
StatusOptional
Datatypeteidata.pointer
quantity(quantity) specifies the number of the specified units that comprise the measurement
StatusOptional
Datatypeteidata.numeric
commodity(commodity) indicates the substance that is being measured
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Note

In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

Schematron
<sch:rule context="tei:*[@unitRef]"> <sch:report test="@unit" role="info">The @unit attribute may be unnecessary when @unitRef is present.</sch:report> </sch:rule>
Note
This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l>So weren't you gonna buy <measure quantity="0.5unit="gal"   commodity="ice cream">half    a gallon</measure>, baby</l> <l>So won't you go and buy <measure quantity="1.893unit="L"   commodity="ice cream">half    a gallon</measure>, baby?</l>

The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

3.35. att.msClass

att.msClass provides attributes to indicate text type or classification.
Modulemsdescription
MembersmsContents msItem msItemStruct
Attributes
classidentifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.36. att.msExcerpt

att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof.
Modulemsdescription
Memberscolophon explicit finalRubric incipit msContents msItem msItemStruct quote rubric
Attributes
defectiveindicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
StatusOptional
Datatypeteidata.xTruthValue
Note

In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.

3.37. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc.
Moduletei
Membersatt.personal[addName forename name orgName persName placeName roleName surname] author birth bloc collection country death district editor event institution occupation offset origPlace pubPlace region repository rs settlement state trait
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

3.38. att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Moduletei
Membersformula quote
Attributes
notationnames the notation used for the content of the element.
StatusOptional
Datatypeteidata.enumerated

3.39. att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name.
Moduletei
MembersaddName forename name orgName persName placeName roleName surname
Attributes
srophe:tagsSpecialized attribute specific to sorting headwords in the Srophe App.
StatusOptional
Datatype1–∞ occurrences of teidata.text separated by whitespace
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort(sort) specifies the sort order of the name component in relation to others within the name.
StatusOptional
Datatypeteidata.count

3.40. att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears.
Moduletei
MembersaddSpan fw head label metamark note witDetail
Attributes
placespecifies where this item is placed.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
top
at the top of the page
bottom
at the foot of the page
margin
in the margin (left, right, or both)
opposite
on the opposite, i.e. facing, page
overleaf
on the other side of the leaf
above
above the line
right
to the right, e.g. to the right of a vertical line of text, or to the right of a figure
below
below the line
left
to the left, e.g. to the left of a vertical line of text, or to the left of a figure
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add> <add place="bottom opposite">[An addition written at the foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

3.41. att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references.
Moduletei
MemberscitedRange licence link locus note ptr ref substJoin witDetail
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
Schematron
<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]"> <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert> </sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">  <ptr xml:id="pol-swh_aln_2.1.1-ptr"   target="pol/UDHR/text.xml#pol_txt_1-head"   type="tuv"   targetLang="pl"/>  <ptr xml:id="pol-swh_aln_2.1.2-ptr"   target="swh/UDHR/text.xml#swh_txt_1-head"   type="tuv"   targetLang="sw"/> </linkGrp>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

targetspecifies the destination of the reference by supplying one or more URI References
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

3.42. att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions[att.damaged[damage damageSpan] addSpan birth date death delSpan depth dim dimensions ex floruit height mod offset origDate redo restore retrace secl space state subst substJoin supplied surplus trait undo width] measure precision
Attributes
atLeastgives a minimum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
StatusOptional
Datatypeteidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
StatusOptional
Datatypeteidata.numeric
confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
StatusOptional
Datatypeteidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">  <gap reason="illegible"   extent="one or two lettersatLeast="1atMost="2unit="chars"/> </del> Philadelphia to the Graphic office, New York.
Example
Americares has been supporting the health sector in Eastern Europe since 1986, and since 1992 has provided <measure atLeast="120000000unit="USD"  commodity="currency">more than $120m</measure> in aid to Ukrainians.

3.43. att.rdgPart

att.rdgPart provides attributes to mark the beginning or ending of a fragmentary manuscript or other witness.
Moduletextcrit
MemberslacunaEnd lacunaStart wit witEnd witStart
Attributes
wit(witness or witnesses) contains a space-delimited list of one or more sigla indicating the witnesses to this reading beginning or ending at this point.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

These elements may appear anywhere within the elements <lem> and <rdg>, and also within any of their constituent elements.

3.44. att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content.
Moduletei
Membersbibl entryFree event idno item list listApp listBibl listPerson listPlace listRelation listWit msDesc person personGrp place relation witness
Attributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatypeteidata.word
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
Note

The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

3.45. att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it.
Moduletei
MembersaddSpan damageSpan delSpan metamark mod redo retrace undo
Attributes
spanToindicates the end of a span initiated by the element bearing this attribute.
StatusOptional
Datatypeteidata.pointer
SchematronThe @spanTo attribute must point to an element following the current element
<sch:rule context="tei:*[@spanTo]"> <sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/> </sch:assert> </sch:rule>
Note

The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

3.46. att.textCritical

att.textCritical defines a set of attributes common to all elements representing variant readings in text critical work.
Moduletextcrit
Memberslem rdg rdgGrp
Attributes
typeclassifies the reading according to some useful typology.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
substantive
(substantive) the reading offers a substantive variant.
orthographic
(orthographic) the reading differs only orthographically, not in substance, from other readings.
causeclassifies the cause for the variant reading, according to any appropriate typology of possible origins.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
homeoteleuton
homeoarchy
paleographicConfusion
haplography
dittography
falseEmendation
varSeq(variant sequence) provides a number indicating the position of this reading in a sequence, when there is reason to presume a sequence to the variants.
StatusOptional
Datatypeteidata.count
Note

Different variant sequences could be coded with distinct number trails: 1-2-3 for one sequence, 5-6-7 for another. More complex variant sequences, with (for example) multiple branchings from single readings, may be expressed through the <join> element.

requirepoints to other readings that are required when adopting the current reading or lemma.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This element class defines attributes inherited by <rdg>, <lem>, and <rdgGrp>.

3.47. att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources.
Moduletei
MembersaddSpan delSpan mod redo restore retrace subst substJoin undo
Attributes
statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
duplicate
all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial
part of the text indicated as an addition duplicates some text that is in the original
excessStart
some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd
some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart
some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd
some text at the end of the deletion is not marked as deleted even though it clearly should be.
partial
some text in the deletion is not marked as deleted even though it clearly should be.
unremarkable
the deletion is not faulty.[Default]
Note

Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.

Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

causedocuments the presumed cause for the intervention.
StatusOptional
Datatypeteidata.enumerated
seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
StatusOptional
Datatypeteidata.count

3.48. att.translatable

att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.
Moduletagdocs
Membersdesc
Attributes
versionDatespecifies the date on which the source text was extracted and sent to the translator
StatusOptional
Datatypeteidata.temporal.working
Note

The versionDate attribute can be used to determine whether a translation might need to be revisited, by comparing the modification date on the containing file with the versionDate value on the translation. If the file has changed, changelogs can be checked to see whether the source text has been modified since the translation was made.

3.49. att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way.
Moduletei
MembersTEI abbr accMat addName addSpan altIdentifier am app bibl birth bloc change collection corr country custEvent damage damageSpan date death decoNote delSpan desc dim dimensions district div event explicit filiation finalRubric forename fw gender head idno incipit label line list listApp listBibl listPerson listPlace listRelation location locus material measure mod msDesc msFrag msName msPart name note occupation offset orgName origDate origPlace path persName place placeName provenance ptr quote ref reg region relation restore roleName rs rubric seal settlement space stamp state surface surfaceGrp surname title trait witDetail zone
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatypeteidata.enumerated
<div type="verse">  <head>Night in Tarras</head>  <lg type="stanza">   <l>At evening tramping on the hot white road</l>   <l></l>  </lg>  <lg type="stanza">   <l>A wind sprang up from nowhere as the sky</l>   <l></l>  </lg> </div>
Note

The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

subtype(subtype) provides a sub-categorization of the element, if needed
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

Schematron
<sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule>
Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 24.3.1.3. Modification of Attribute and Attribute Value Lists .

3.50. att.witnessed

att.witnessed provides attributes used to identify the witnesses supporting a particular reading in a critical apparatus.
Moduletextcrit
Memberslem rdg
Attributes
wit(witness or witnesses) contains a space-delimited list of one or more pointers indicating the witnesses which attest to a given reading.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

If the apparatus contains readings only for a single witness, this attribute may be consistently omitted.

This attribute may occur both within an apparatus gathering variant readings in the transcription of an individual witness and within an apparatus gathering readings from different witnesses.

Additional descriptions or alternative versions of the sigla referenced may be supplied as the content of a child <wit> element.

3.51. att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed.
Moduletei
Membersatt.damaged[damage damageSpan] att.textCritical[lem rdg rdgGrp] att.transcriptional[addSpan delSpan mod redo restore retrace subst substJoin undo] div fw head label line note p path zone
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
StatusOptional
Datatypeteidata.pointer

4. Macros

4.1. macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
tei_macro.limitedContent =
   ( text | tei_model.limitedPhrase | tei_model.inter )*

4.2. macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    
Declaration
tei_macro.paraContent = ( text | tei_model.paraPart )*

4.3. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq =
   (
      text
    | tei_model.gLike
    | tei_model.attributable
    | tei_model.phrase
    | tei_model.global
   )*

4.4. macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq.limited =
   ( text | tei_model.limitedPhrase | tei_model.global )*

4.5. macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.specialPara =
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.divPart
    | tei_model.global
   )*

4.6. macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
    
Declaration
tei_macro.xtext = ( text | tei_model.gLike )*

5. Datatypes

5.1. teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
Used by
teidata.probCertElement:
Content model
<content>
 <valList type="closed">
  <valItem ident="high"/>
  <valItem ident="medium"/>
  <valItem ident="low"/>
  <valItem ident="unknown"/>
 </valList>
</content>
    
Declaration
tei_teidata.certainty = "high" | "medium" | "low" | "unknown"
Note

Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

5.2. teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
    
Declaration
tei_teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

5.3. teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei
Used by
teidata.gender teidata.sexElement:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
    
Declaration
tei_teidata.enumerated = teidata.word
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

5.4. teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
tei_teidata.gender = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 10.3.1. Information on Written and Spoken Forms).

5.5. teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system.
Moduletei
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.language = xsd:language | ( "" )
Note

The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at https://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at https://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes ‘are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags’.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

Examples include

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

5.6. teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Moduletei
Used by
Content model
<content>
 <dataRef name="Name"/>
</content>
    
Declaration
tei_teidata.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

5.7. teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Moduletei
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef name="double"/>
  <dataRef name="token"
   restriction="(\-?[\d]+/\-?[\d]+)"/>
  <dataRef name="decimal"/>
 </alternate>
</content>
    
Declaration
tei_teidata.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
Note

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

5.8. teidata.point

teidata.point defines the data type used to express a point in cartesian space.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
    
Declaration
tei_teidata.point =
   token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
Example
<facsimile>  <surface ulx="0uly="0lrx="400lry="280">   <zone points="220,100 300,210 170,250 123,234">    <graphic url="handwriting.png"/>   </zone>  </surface> </facsimile>
Note

A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

5.9. teidata.pointer

teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
tei_teidata.pointer = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

5.10. teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef key="teidata.probability"/>
  <dataRef key="teidata.certainty"/>
 </alternate>
</content>
    
Declaration
tei_teidata.probCert = teidata.probability | teidata.certainty

5.11. teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Moduletei
Used by
Content model
<content>
 <dataRef name="double">
  <dataFacet name="minInclusive" value="0"/>
  <dataFacet name="maxInclusive" value="1"/>
 </dataRef>
</content>
    
Declaration
tei_teidata.probability = xsd:double
Note

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

5.12. teidata.sex

teidata.sex defines the range of attribute values used to identify the sex of an organism.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
tei_teidata.sex = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

5.13. teidata.temporal.iso

teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
  <dataRef name="token"
   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.iso =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
 | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

5.14. teidata.temporal.w3c

teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Moduletei
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

5.15. teidata.temporal.working

teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef name="date"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
  <dataRef name="dateTime"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.working =
   xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
 | xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z.

5.16. teidata.text

teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="string"/>
</content>
    
Declaration
tei_teidata.text = string
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

5.17. teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="boolean"/>
</content>
    
Declaration
tei_teidata.truthValue = xsd:boolean
Note

The possible values of this datatype are 1 or true, or 0 or false.

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

5.18. teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
    
Declaration
tei_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

5.19. teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Moduletei
Used by
teidata.enumeratedElement:
Content model
<content>
 <dataRef name="token"
  restriction="[^\p{C}\p{Z}]+"/>
</content>
    
Declaration
tei_teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

5.20. teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Moduletei
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef name="boolean"/>
  <valList>
   <valItem ident="unknown"/>
   <valItem ident="inapplicable"/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
Note

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

5.21. teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Moduletei
Used by
Element:
Content model
<content>
 <textNode/>
</content>
    
Declaration
tei_teidata.xpath = text
Note

Any XPath expression using the syntax defined in 6.2..

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

Date: